Re: pgsql: Prevent invalidation of newly synced replication slots.

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-01-27T16:11:08Z

Lists: pgsql-hackers

Robert Haas <robertmhaas@gmail.com> writes:
> What's also puzzling is that what this test is doing seems to be
> totally standard.

Yeah.  I do notice something interesting when running it here:
046_checkpoint_logical_slot_mike.log shows that we are triggering
quite a few checkpoints (via pg_switch_wal()) in quick succession
on the primary.  I wonder if that is somehow tickling a Windows
filesystem restriction.

			regards, tom lane

Commits

Fix CI failure introduced in commit 851f6649cc.
- 1c60f7236368 18.2 landed
- 3a98f989e8e5 19 (unreleased) landed
- 9649f1adfdee 17.8 landed
Prevent invalidation of newly synced replication slots.
- 851f6649cc18 19 (unreleased) cited
Prevent invalidation of newly created replication slots.
- 006dd4b2e5b3 19 (unreleased) cited