Re: Move system identifier generation to a common helper - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Move system identifier generation to a common helper
Date
Msg-id 954FFDCA-2DA8-4B8E-84A9-62FFC0C5C5E9@yesql.se
Whole thread
In response to Re: Move system identifier generation to a common helper  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Move system identifier generation to a common helper
List pgsql-hackers
> On 10 Jun 2026, at 15:25, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> On 04.06.26 14:22, Imran Zaheer wrote:
>> The code used to generate a new system identifier is duplicated in
>> multiple locations, including BootStrapXLOG(), pg_createsubscriber, and
>> pg_resetwal.
>> Move the generation logic into a common GenerateSystemIdentifier()
>> helper so that all callers use a single implementation, avoiding
>> duplication of the same algorithm.
>
> Then again, this code is from PG 8.0.  We have had pg_strong_random() required since PG 12.  Maybe we should use that
nowfor this. 

One feature of the current scheme is that it's explicitly not random, but can
be reverse-engineered to figure out the init time.  Maybe we should have a
better way of doing that regardless, but it doesn't seem like a bad feature to
keep.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Commit Sequence Numbers and Visibility
Next
From: Andres Freund
Date:
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st