Re: ci: namespace ccache by PostgreSQL major version

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: ci: namespace ccache by PostgreSQL major version
Date: 2026-07-06 08:05:31
Message-ID: CAN55FZ3L2BwOw0b=VstDekU6mu9c=40iNXAsSMYvYRGyfYXPnw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Mon, 6 Jul 2026 at 10:52, Peter Eisentraut <peter(at)eisentraut(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilmar Yunusov 2026-07-06 08:14:08 Re: generic plans and "initial" pruning
Previous Message Shlok Kyal 2026-07-06 08:00:41 Re: Include sequences in publications created by pg_createsubscriber