Re: Inconsistent LSN format in pg_waldump output
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Japin Li <japinli@hotmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Masahiko Sawada <sawada.mshk@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-03T16:07:45Z
Lists: pgsql-hackers
On 2025-Jul-03, Japin Li wrote: > Providing two LSN formats — %X%08X for translatable messages and > LSN_FORMAT for non-translatable ones — seems to offer no clear advantage. > > I'd prefer to use %X/%08X directly and add the description to the > LSN_FORMAT_ARGS macro. WFM. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "La gente vulgar sólo piensa en pasar el tiempo; el que tiene talento, en aprovecharlo"
Commits
-
Fix a couple more places in docs for pg_lsn change
- aa39b4e35ac6 19 (unreleased) landed
-
Adapt pg_upgrade test to pg_lsn output format difference
- 3adcf9fbd8ba 19 (unreleased) landed
-
Standardize LSN formatting by zero padding
- 2633dae2e487 19 (unreleased) landed