Re: libpq-oauth: a mid-beta naming check - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: libpq-oauth: a mid-beta naming check
Date
Msg-id aJImz3tzipRbixpY@msg.df7cb.de
Whole thread Raw
In response to Re: libpq-oauth: a mid-beta naming check  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-hackers
Re: Jacob Champion
> On Tue, Aug 5, 2025 at 2:39 AM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> > On Tue, 5 Aug 2025 at 01:20, Jacob Champion
> > <jacob.champion@enterprisedb.com> wrote:
> > > So, as we approach Beta 3: can anyone think of a way that this plan will fail?
> >
> > It's not entirely clear what plan exactly you talk about here. Are you
> > saying you want to remove the -MAJOR suffix now for PG18? Or you want
> > to postpone doing that until PG19, when you would have designed a
> > stable API?
> 
> That is a PG19 plan. I don't want to make any changes for 18 unless
> someone can see a fatal flaw; this is just my mid-beta check.

FTR, fine with me.

> > If your goal is to remove this
> > during-upgrade breakage after PG19, then I'd say that seems totally
> > fine for a new feature.
> 
> That's the hope, yes.

Well, at the PG19 release time it will no longer be new. But the plan
sounds like a good one.

Christoph



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Improve LWLock tranche name visibility across backends
Next
From: Peter Eisentraut
Date:
Subject: Re: Convert varatt.h macros to static inline functions