Re: Timeline ID hexadecimal format
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Sébastien Lardière <sebastien@lardiere.net>, pgsql-hackers@postgresql.org
Date: 2023-01-27T14:55:11Z
Lists: pgsql-hackers
On 27.01.23 14:52, Sébastien Lardière wrote: > The attached patch proposes to change the format of timelineid from %u > to %X. I think your complaint has merit. But note that if we did a change like this, then log files or reports from different versions would have different meaning without a visual difference, which is kind of what you complained about in the first place. At least we should do something like 0x%X. > Regarding .po files, I don't know how to manage them. Is there any > routine to spread the modifications? Or should I identify and change > each message? Don't worry about this. This is handled elsewhere.
Commits
-
pg_waldump: Allow hexadecimal values for -t/--timeline option
- 4c8044c04455 16.0 landed
-
doc: Additional information about timeline ID hexadecimal format
- 0b51d423e974 16.0 landed