Re: Heads Up: cirrus-ci is shutting down June 1st - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id yhst2iacmavxsqlsrjkqsjodtf7finznzwrc7dm5dzkf3ygg3w@l6q2grflyjqx
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Heads Up: cirrus-ci is shutting down June 1st
Re: Heads Up: cirrus-ci is shutting down June 1st
Re: Heads Up: cirrus-ci is shutting down June 1st
List pgsql-hackers
Hi,

On 2026-06-04 09:02:13 -0700, Jacob Champion wrote:
> On Thu, Jun 4, 2026 at 9:00 AM Andres Freund <andres@anarazel.de> wrote:
> > > On the CPAN front, my first attempt tried to do too much, so I'm
> > > testing a solution that just caches the CPAN sources directory. Should
> > > have something shortly.
> >
> > I'm kinda inclined to push what we have and then add the cpan caching on top
> > in subsequent commits?
> 
> Right -- I don't think v1 should wait on CPAN optimization; I just
> wanted to let you know the status.

Pushed it now. Only a tiny change from the last version, Bilal suggested ove
IM to remove the multi-threading argument from robocopy, for performance.

I did futz around with ccache improvements for a bit. I think we're going to
need them, but they're complicated enough to do them separately.


Thanks to Bilal, Jelte and all the review!


Greetings,

Andres



pgsql-hackers by date:

Previous
From: Denis Rodionov
Date:
Subject: Re: [PATCH] Remove obsolete tupDesc assignment in extended statistics
Next
From: Zsolt Parragi
Date:
Subject: Re: Fix bug of CHECK constraint enforceability recursion