| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ci: namespace ccache by PostgreSQL major version |
| Date: | 2026-07-17 13:06:40 |
| Message-ID: | e7s3m4cf5x5zekytuadq64jqswrlfsn2fckxq55k4bk3otsa5i@s6br4pdbbtkr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2026-07-17 13:50:30 +0200, Jelte Fennema-Nio wrote:
> On Fri, 17 Jul 2026 at 11:41, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> > 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.
>
> Sure, but it would be nice to be able to create a shared cache by
> pushing REL_19_STABLE if you're backporting multiple things.
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.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nurlan Tulemisov | 2026-07-17 13:09:40 | Re: postgres_fdw: Emit message when batch_size is reduced |
| Previous Message | Boris Mironov | 2026-07-17 12:50:15 | Yet another PG extension to support Gzip, LZ4, Zstd functions optimized for multi-megabyte documents |