Re: Sequence Access Methods, round two

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Peter Smith <smithpb2250@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-08-30T08:24:19Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Refactor init_params() in sequence.c to not use FormData_pg_sequence_data

  2. Fix comment thinko in sequence.c

  3. Group more closely cache updates for backends in sequence.c

  4. Introduce sequence_*() access functions

Attachments

On Mon, Aug 26, 2024 at 01:45:12PM +0900, Michael Paquier wrote:
> Finally, I have been rather annoyed by the addition of log_cnt in the
> new function pg_sequence_read_tuple().  This patch set could also
> implement a new system function, but it looks like a waste as we don't
> care about log_cnt in pg_dump and pg_upgrade on HEAD, so I'm proposing
> to remove it on a different thread:
> https://www.postgresql.org/message-id/Zsvka3r-y2ZoXAdH%40paquier.xyz

Following a83a944e9fdd, rebased as v8.
--
Michael