Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, orlovmg@gmail.com, alvherre@alvh.no-ip.org, nathandbossart@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2022-12-20T00:01:02Z
Lists: pgsql-hackers
On Mon, Dec 19, 2022 at 05:51:19PM +0530, Bharath Rupireddy wrote: > A nitpick - can we also specify a use case for the function > pg_dissect_walfile_name(), that is, computing LSN from offset and WAL > file name, something like [1]? Yeah, my mind was considering as well yesterday the addition of a note in the docs about something among these lines, so fine by me. -- Michael
Commits
-
Rename pg_dissect_walfile_name() to pg_split_walfile_name()
- 13e0d7a60385 16.0 landed
-
Add pg_dissect_walfile_name()
- cca186348929 16.0 landed
-
Add LSN location in some error messages related to WAL pages
- 71cb84ec69a3 16.0 landed