From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
Subject: | Re: Adding CI to our tree |
Date: | 2021-12-18 13:29:01 |
Message-ID: | 45d22085-fb86-543e-514f-0721fcb394c5@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/17/21 14:34, Andres Freund wrote:
> Hi,
>
> On 2021-12-17 09:36:05 -0500, Tom Lane wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>> Maye I have missed it, but why are we using ccache here? That seems a
>>> bit pointless in an ephemeral instance.
>> I believe Munro's cfbot tooling is able to save and re-use ccache
>> across successive instantiations of a build instance. I've not
>> looked at this code, but if it can do that there'd be point to it.
> Yes, the ccache cache is persisted across runs (see the *_cache and
> upload_cache inststructions). It makes a quite substantial difference. One
> reason the windows runs are a lot slower than the others is just that visual
> studio isn't yet supported by ccache, and that there doesn't seem to be good
> other tools.
>
> The ccache maintainers merged more of the msvc support last weekend! So I have
> quite a bit of hope of being able to use ccache there as well.
>
Ok. I have had to disable ccache for fairywren (msys2) because it caused
serious instability.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-12-18 16:51:56 | Re: Column Filtering in Logical Replication |
Previous Message | Michael Paquier | 2021-12-18 11:29:22 | Refactoring of compression options in pg_basebackup |