Re: ci: namespace ccache by PostgreSQL major version - Mailing list pgsql-hackers

From Nazir Bilal Yavuz
Subject Re: ci: namespace ccache by PostgreSQL major version
Date
Msg-id CAN55FZ2FNoGevdRKjD4e=EHXFMexnsDCGTYpBwzP0t5ZcR3m2A@mail.gmail.com
Whole thread
In response to Re: ci: namespace ccache by PostgreSQL major version  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: ci: namespace ccache by PostgreSQL major version
List pgsql-hackers
Hi,

On Fri, 17 Jul 2026 at 01:19, Jelte Fennema-Nio <postgres@jeltef.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



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: [PATCH] Don't call ereport(ERROR) from recovery target GUC assign hooks
Next
From: Etsuro Fujita
Date:
Subject: Re: use of SPI by postgresImportForeignStatistics