From 4d04db3fbd78b1ab36a91ac8fd04ad2904ee089f Mon Sep 17 00:00:00 2001 From: "Chao Li (Evan)" Date: Tue, 29 Sep 2026 08:49:48 +0800 Subject: [PATCH v1] Document replication slot handling with pg_resetwal --wal-segsize MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changing the WAL segment size discards the previous WAL history, making existing replication slots unusable. Document that replication slots must be dropped before changing the segment size and recreated afterward, and that standby servers must be rebuilt from new base backups. Reported-by: Rıdvan Korkmaz Author: Chao Li --- doc/src/sgml/ref/pg_resetwal.sgml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/src/sgml/ref/pg_resetwal.sgml b/doc/src/sgml/ref/pg_resetwal.sgml index d34aa26413c..6d3eeaecf06 100644 --- a/doc/src/sgml/ref/pg_resetwal.sgml +++ b/doc/src/sgml/ref/pg_resetwal.sgml @@ -399,6 +399,14 @@ PostgreSQL documentation re-initdb. + + Before changing the WAL segment size, drop all replication slots. + Existing standby servers cannot continue replication after the reset + because the previous WAL history has been discarded. After the reset, + recreate the replication slots and rebuild the standby servers from new + base backups. + + While pg_resetwal will set the WAL starting address -- 2.50.1 (Apple Git-155)