Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: michael@paquier.xyz, orlovmg@gmail.com, alvherre@alvh.no-ip.org, nathandbossart@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2022-12-13T16:02:19Z
Lists: pgsql-hackers
Attachments
- v5-0001-Add-utility-functions-to-disset-WAL-file-name-and.patch (application/x-patch) patch v5-0001
On Tue, Dec 6, 2022 at 4:46 PM Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> wrote: > > That said, I think we can have a single function > pg_dissect_walfile_name(wal_file_name, offset optional) returning > segno (XLogSegNo - physical log file sequence number), tli, lsn (if > offset is given). This way there is no need for another SQL-callable > function using pg_settings. Thoughts? > > > (If we assume that the file names are typed in letter-by-letter, I > > rather prefer to allow lower-case letters:p) > > It's easily doable if we convert the entered WAL file name to > uppercase using pg_toupper() and then pass it to IsXLogFileName(). Okay, here's the v5 patch that I could come up with. It basically adds functions for dissecting WAL file names and computing offset from lsn. Thoughts? -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
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