Re: pg_sequence_last_value() for unlogged sequences on standbys - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: pg_sequence_last_value() for unlogged sequences on standbys
Date
Msg-id 20240501020531.GA721953@nathanxps13
Whole thread Raw
In response to Re: pg_sequence_last_value() for unlogged sequences on standbys  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: pg_sequence_last_value() for unlogged sequences on standbys
List pgsql-hackers
On Tue, Apr 30, 2024 at 08:13:17PM -0500, Nathan Bossart wrote:
> Good point.  I'll work on a patch along these lines, then.

This ended up being easier than I expected.  While unlogged sequences are
only supported on v15 and above, temporary sequences have been around since
v7.2, so this will probably need to be back-patched to all supported
versions.  The added test case won't work for v12-v14 since it uses an
unlogged sequence.  I'm not sure it's worth constructing a test case for
temporary sequences.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: pg_sequence_last_value() for unlogged sequences on standbys
Next
From: Noah Misch
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.