Re: New standby_slot_names GUC in PG 17 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New standby_slot_names GUC in PG 17
Date
Msg-id 771727.1719067433@sss.pgh.pa.us
Whole thread Raw
In response to Re: New standby_slot_names GUC in PG 17  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> FYI, changing this GUC name could force an initdb because
> postgresql.conf would have the old name and removing the comment to
> change it would cause an error.  Therefore, we should change it ASAP.

That's not reason for a forced initdb IMO.  It's easily fixed by
hand.

At this point we're into the release freeze for beta2, so even
if we had consensus on a new name it should wait till after.
So I see no particular urgency to make a decision.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: FreezeLimit underflows in pg14 and 15 causing incorrect behavior in heap_prepare_freeze_tuple
Next
From: Peter Geoghegan
Date:
Subject: Re: FreezeLimit underflows in pg14 and 15 causing incorrect behavior in heap_prepare_freeze_tuple