Re: unlogged sequences - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: unlogged sequences
Date
Msg-id 3da1154b-54b2-719c-c04b-f0cb50735a10@enterprisedb.com
Whole thread Raw
In response to Re: unlogged sequences  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On 06.04.22 11:12, Peter Eisentraut wrote:
> We could also move forward with this patch independently of the other 
> one.  If we end up reverting the other one, then this one won't be very 
> useful but it won't really hurt anything and it would presumably become 
> useful eventually.  What we presumably don't want is that the sequence 
> replication patch gets repaired for PG15 and we didn't end up committing 
> this patch because of uncertainty.

I have received some encouragement off-list to go ahead with this, so 
it's been committed.




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.]
Next
From: Justin Pryzby
Date:
Subject: Re: How about a psql backslash command to show GUCs?