Re: ci: namespace ccache by PostgreSQL major version

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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 11:50:30
Message-ID: CAGECzQRED+rmO8n6hmBKifuCAD2rMaOWTaWkYaiC2Oe6-VP+bQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-07-17 11:53:31 Re: sequencesync worker race with REFRESH SEQUENCES
Previous Message Antonin Houska 2026-07-17 11:22:37 Re: Batching in executor