Horton

Re: Sequence Access Methods, round two

Andrei Lepikhov <lepihov@gmail.com>

View thread
From: Andrei Lepikhov <lepihov@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Xuneng Zhou <xunengzhou@gmail.com>, Chao Li <li.evan.chao@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Kirill Reshke <reshkekirill@gmail.com>, Peter Smith <smithpb2250@gmail.com>
Date: 2026-05-18T18:42:51Z
Lists: pgsql-hackers

Attachments

On 18/05/2026 00:43, Michael Paquier wrote:
> On Sun, May 17, 2026 at 08:03:15AM +0200, Andrei Lepikhov wrote:
>> Right now, awaiting this feature, I use a nextval hook. But it is just to
>> minimise the number of core lines that need to be changed. Neither hook nor
>> callback is a good idea here - sequence source might be only one for a specific
>> table; \d should show an unequivocal definition of a table.
>> Also, the AM machinery makes the dump/restore use cases clear. Logical
>> replication plugins also benefit from it: pgactive, pglogical, and spock all
>> include Auto-DDL solutions that simplify the management of sequence generation
>> methods across instances.
> 
> There was zero feedback from other core developers, so it's really
> hard to weigh about its acceptance.  My guess is that nobody really
> cares about this thread, which is just the way it is on -hackers for
> some things.  FWIW, I still like what I've done in this patch and this
> design.

Ok. So let me just leave the idea of avoiding unnecessary cache lookups here.

-- 
regards, Andrei Lepikhov,
pgEdge