Re: Sequence Access Methods, round two - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Sequence Access Methods, round two
Date
Msg-id aLUiKeqm2Lxta7Uz@paquier.xyz
Whole thread Raw
In response to Re: Sequence Access Methods, round two  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Sequence Access Methods, round two
List pgsql-hackers
On Thu, Aug 21, 2025 at 11:57:58AM +0900, Michael Paquier wrote:
> Yes, that may be useful, but I don't think that this should use the
> psql variable to hide table AMs.  I am rebasing a new patch set, v18,
> with a couple of changes:
> - Added your feedback about psql.
> - I have put more thoughts into the code shared between the in-core
> sequence method and the snowflake one, and looked at reducing the
> duplication between the two.  At the end, I have introduced a new
> header called sequence_page.h, which is able to reduce the work for
> AMs when these rely on a single page through the addition of macros
> able to initialize and read sequence pages.  In this patch set, this
> new part is labelled with 0006.
> - Fixed a few more things, like comments.

Another rebase required due to the business with BufferGetPage() in
710e6c4301ee.

By the way, I have remembered the reason why I have introduced
AT_AddColumnToSequence as a new ALTER TABLE subcommands: ACL check for
sequences.  Like views, this simplifies the object type check a lot.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alexandra Wang
Date:
Subject: Re: SQL:2023 JSON simplified accessor support
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Conflict detection for update_deleted in logical replication