Re: Timeline ID hexadecimal format

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Sébastien Lardière <sebastien(at)lardiere(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Timeline ID hexadecimal format
Date: 2023-03-03 16:04:14
Message-ID: CA+TgmoacF8hK5T6Nm5g=fEKCRON8ELYYJabCnmyYLFLW9RJyFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 31, 2023 at 2:16 PM Greg Stark <stark(at)mit(dot)edu> wrote:
> I don't see any advantage in converting every place where we refer to
> timelines into hex and then having to refer to things like timeline
> 1A. It doesn't seem any more intuitive to someone understanding what's
> going on than referring to timeline 26.

The point, though, is that the WAL files we have on disk already say
1A. If we change the log messages to match, that's easier for users.
We could alternatively change the naming convention for WAL files on
disk, but that feels like a much bigger compatibility break.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeroen Vermeulen 2023-03-03 16:16:05 Re: libpq: PQgetCopyData() and allocation overhead
Previous Message Robert Haas 2023-03-03 16:02:30 running logical replication as the subscription owner