Re: ci: namespace ccache by PostgreSQL major version

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ci: namespace ccache by PostgreSQL major version
Date: 2026-07-16 22:19:33
Message-ID: CAGECzQQ6auMC+Y8sRySYR7dphR-o8PDw4=L5LvvFFPAw-4GOUg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 16 Jul 2026 at 23:27, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Attached is the change I propose.

Seems reasonable (assuming it indeed fixes the issue)

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.

To be clear, this would look quite different from Bilal's patch.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2026-07-16 22:35:30 Re: Why clearing the VM doesn't require registering vm buffer in wal record
Previous Message Peter Geoghegan 2026-07-16 22:11:18 Re: Hash index AM fake LSN oversight