Re: Sequence Access Methods, round two

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, Peter Smith <smithpb2250@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-19T07:00:28Z
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 Tue, Mar 19, 2024 at 10:54:41AM +0900, Michael Paquier wrote:
> I am not sure where this is leading in combination with the sequence
> stuff for logical decoding, so for now I am moving this patch to the
> next commit fest to discuss things in 18~.

I have plans to rework this patch set for the next commit fest,
and this includes some investigation about custom data types that
could be plugged into these AMs.  For now, please find a rebase as
there were a couple of conflicts.
--
Michael