Re: [Proposal] global sequence implemented by snowflake ID

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [Proposal] global sequence implemented by snowflake ID
Date: 2023-11-23 10:45:07
Message-ID: ZV8tM_5n_53BOzVz@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 23, 2023 at 10:18:59AM +0000, Hayato Kuroda (Fujitsu) wrote:
> * Implement as a variant of sequence access method. I found that sequence AM was
> proposed many years ago [5], but it has not been active now. It might be a
> fundamental way but needs a huge works.

Well, that's what I can call a timely proposal. I've been working
this week on a design for sequence AMs, while considering the cases
that the original thread wanted to handle (spoiler: there are a lot of
pieces in the original patch that are not necessary, other parts are
incorrect like dump/restore), what you are trying to do here, and more
complex scenarios in terms of globally-distributed sequences. My plan
was to send that next week or the week after, in time for January's
CF.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-11-23 10:45:34 Re: Synchronizing slots from primary to standby
Previous Message John Naylor 2023-11-23 10:41:08 Re: Change GUC hashtable to use simplehash?