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

From Jacob Champion
Subject Re: ci: namespace ccache by PostgreSQL major version
Date
Msg-id CAOYmi+mv3NQLf2=2SqwZQi6sEx5DqqsYde03gcS+dhtojBtibw@mail.gmail.com
Whole thread
In response to Re: ci: namespace ccache by PostgreSQL major version  (Andres Freund <andres@anarazel.de>)
Responses Re: ci: namespace ccache by PostgreSQL major version
List pgsql-hackers
On Fri, Jul 17, 2026 at 6:06 AM Andres Freund <andres@anarazel.de> wrote:
> That's how it works. We restore the cache for master and for the current
> branch. We save the cache, after pruning it, for the current branch iff the
> hit rate was < 80%.
>
> It'd be nice if we could restore the cache for the "base branch" of a branch,
> instead of master, but that's not currently possible in GHA, from what I can
> tell. Only caches on the default branch are accessible to other branches.

Quick tangent: is there a reason we put the refname into the cache
key? It seems like some of the logic there would happen by default if
we used the same cache prefix for all branches, since I thought GitHub
would perform the fallback-to-default-branch for us.

--Jacob



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Deprecation warnings on Rocky 10.2 with current dev branch
Next
From: Andres Freund
Date:
Subject: Re: ci: namespace ccache by PostgreSQL major version