From 344afc77690b4cef2605420d67c1d1ceb28760cc Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 24 Nov 2023 19:44:09 -0500 Subject: modify segno. for pg_walfile_name() and pg_walfile_name_offset() Previously these functions returned the previous segment number if the LSN was on a segment boundary. We now always return the current segment number for an LSN. Docs updated to reflect this change. Regression tests added, author Andres Freund. Also mentioned in thread https://postgr.es/m/flat/20220204225057.GA1535307%40nathanxps13#d964275c9540d8395e138efc0a75f7e8 BACKWARD INCOMPATIBILITY Reported-by: Kyotaro Horiguchi Discussion: https://postgr.es/m/20190726.172120.101752680.horikyota.ntt@gmail.com Co-authored-by: Kyotaro Horiguchi Backpatch-through: master --- doc/src/sgml/func.sgml | 5 ----- 1 file changed, 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 053fbc5ef2c..20da3ed0334 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -27075,11 +27075,6 @@ postgres=# SELECT * FROM pg_walfile_name_offset((pg_backup_stop()).lsn); (1 row) Similarly, pg_walfile_name extracts just the write-ahead log file name. - When the given write-ahead log location is exactly at a write-ahead log file boundary, both - these functions return the name of the preceding write-ahead log file. - This is usually the desired behavior for managing write-ahead log archiving - behavior, since the preceding file is the last one that currently - needs to be archived. -- cgit v1.2.3