Re: Timeline ID hexadecimal format

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Sébastien Lardière <sebastien(at)lardiere(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Timeline ID hexadecimal format
Date: 2023-01-31 09:53:21
Message-ID: e4420b51-a2ea-bbb6-db2c-c6c46765858a@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.01.23 17:05, Sébastien Lardière wrote:
>
> Here's the patch with the suggested format ; plus, I add some note in
> the documentation about recovery_target_timeline, because I don't get
> how strtoul(), with the special 0 base parameter can work without 0x
> prefix ; I suppose that nobody use it.
>
> I also change pg_controldata and the usage of this output by pg_upgrade.
> I let internal usages unchanded : content of backup manifest and content
> of history file.
>
> Should I open a commitfest entry, or is it too soon ?

It is not too soon. (The next commitfest is open for new patch
submissions as soon as the current one is "in progress", which closes it
for new patches.)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-01-31 09:55:30 Re: Allow tests to pass in OpenSSL FIPS mode
Previous Message Amit Kapila 2023-01-31 09:42:14 Re: Time delayed LR (WAS Re: logical replication restrictions)