Re: Log a warning in pg_createsubscriber for max_slot_wal_keep_size
Shubham Khanna <khannashubham1197@gmail.com>
From: Shubham Khanna <khannashubham1197@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-09T06:53:10Z
Lists: pgsql-hackers
Attachments
- v7-0001-Validate-max_slot_wal_keep_size-in-pg_createsubsc.patch (application/octet-stream) patch v7-0001
On Mon, Jan 6, 2025 at 3:22 AM Peter Smith <smithpb2250@gmail.com> wrote: > > Hi Shubham. > > The patch v6-0001 LGTM. > > OTOH, if you want to be picky, the docs wording could be slightly > modified to be more consistent with the coded warning message. > > CURRENT > Replication failures can occur if required WAL files are prematurely > deleted. To prevent this, the source server must set <xref > linkend="guc-max-slot-wal-keep-size"/> to <literal>-1</literal>, > ensuring WAL files are not automatically removed. > > SUGGESTION > Replication failures can occur if required WAL files are missing. To > prevent this, the source server must set <xref > linkend="guc-max-slot-wal-keep-size"/> to <literal>-1</literal> to > ensure that required WAL files are not prematurely removed. > > ~~~ > > See the attached NITPICKS diff if you want to make this change. > I have used your suggestion and updated the 'pg_createsubscriber' documentation accordingly. The attached Patch contains the suggested change. Thanks and regards, Shubham Khanna.
Commits
-
Raise a WARNING for max_slot_wal_keep_size in pg_createsubscriber.
- 217919dd0954 18.0 landed
-
Improve grammar of options for command arrays in TAP tests
- ce1b0f9da03e 18.0 cited