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 CAN55FZ3L2BwOw0b=VstDekU6mu9c=40iNXAsSMYvYRGyfYXPnw@mail.gmail.com
Whole thread
In response to Re: ci: namespace ccache by PostgreSQL major version  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
Hi,

On Mon, 6 Jul 2026 at 10:52, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> On 03.07.26 16:26, Nazir Bilal Yavuz wrote:
> > Hi,
> >
> > This happens because the GitHub Actions ccache is restored across a
> > version bump, so objects built against the previous version can be
> > reused, producing libraries that no longer match the server version.
> >
> > Here is an attempt to solve this problem by namespacing ccache by
> > Postgres major version.
>
> I'm suspicious about this direction.  The major version is not the only
> piece of data that determines ABI compatibility between the server and
> extensions.  This would only be a partial information.  The ABI
> information exists in the code, and so changes should be visible to
> ccache.  Maybe we are using ccache in the wrong mode or something (see
> "depend mode", "direct mode", etc.).

Thanks for the feedback!

Yes, you are right. I realized that after doing the further research
(I should have done that sooner, before sending the patch).

-- 
Regards,
Nazir Bilal Yavuz
Microsoft



pgsql-hackers by date:

Previous
From: Shlok Kyal
Date:
Subject: Re: Include sequences in publications created by pg_createsubscriber
Next
From: Ilmar Yunusov
Date:
Subject: Re: generic plans and "initial" pruning