| From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ci: namespace ccache by PostgreSQL major version |
| Date: | 2026-07-17 09:41:04 |
| Message-ID: | CAN55FZ2FNoGevdRKjD4e=EHXFMexnsDCGTYpBwzP0t5ZcR3m2A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Fri, 17 Jul 2026 at 01:19, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>
> Regardless, I think we should still scope the caches on PG version
> though for a completely different reason: Any backpatches (currently
> only to 19) will become less and less cached as PG20 diverges from
> PG19 if we have a shared cache. We should in addition make sure that
> we create shared cached from REL_XX_STABLE branches and generate their
> cache keys in a way that other branches restore them.
AFAIK, if the cache hit ratio is below some point
(gha_ccache_decide.py -> 80 for branches other than master), the
branch regenerates its own cache. So, this shouldn't be a problem.
--
Regards,
Nazir Bilal Yavuz
Microsoft
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2026-07-17 09:59:59 | Re: use of SPI by postgresImportForeignStatistics |
| Previous Message | Fujii Masao | 2026-07-17 09:30:14 | Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks |