| 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-27 14:55:11 |
| Message-ID: | 6a5ab26f-3737-c77f-1400-341ef75d1eef@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-01-27 14:57:45 | Re: run pgindent on a regular basis / scripted manner |
| Previous Message | Robert Haas | 2023-01-27 14:53:29 | Re: New strategies for freezing, advancing relfrozenxid early |