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: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: bharath.rupireddyforpostgres@gmail.com, magnus@hagander.net, orlovmg@gmail.com, alvherre@alvh.no-ip.org, nathandbossart@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2022-12-22T11:27:32Z
Lists: pgsql-hackers
On Thu, Dec 22, 2022 at 05:19:24PM +0900, Kyotaro Horiguchi wrote: > In the first place "file sequence number" and "segno" can hardly be > associated by appearance by readers, I think. (Yeah, we can identify > that since the another parameter is identifiable alone.) Why don't we > spell out the parameter simply as "segment number"? As in using "sequence number" removing "file" from the docs and changing the OUT parameter name to segment_number rather than segno? 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