Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1vkler-001tGP-2W
	for pgsql-hackers@arkaria.postgresql.org;
	Tue, 27 Jan 2026 16:11:14 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1vkleq-00Eb60-2s
	for pgsql-hackers@arkaria.postgresql.org;
	Tue, 27 Jan 2026 16:11:13 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vkleq-00Eb5r-1u
	for pgsql-hackers@lists.postgresql.org;
	Tue, 27 Jan 2026 16:11:12 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.98.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1vkleo-00000000jIO-2oEx
	for pgsql-hackers@lists.postgresql.org;
	Tue, 27 Jan 2026 16:11:12 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 60RGB8oD547220;
	Tue, 27 Jan 2026 11:11:08 -0500
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>
Subject: Re: pgsql: Prevent invalidation of newly synced replication slots.
In-reply-to: 
 <CA+TgmoYvtJoU0eyw3XEmLLda_JV4qSJxJpVfoTtFL3uPs5+7vw@mail.gmail.com>
References: <E1vkc3p-002uNr-0e@gemulon.postgresql.org>
 <CA+TgmobdVhO0ckZfsBZ0wqDO4qHVCwZZx8sf=EinafvUam-dsQ@mail.gmail.com>
 <428236.1769526672@sss.pgh.pa.us>
 <CA+TgmoYvtJoU0eyw3XEmLLda_JV4qSJxJpVfoTtFL3uPs5+7vw@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Tue, 27 Jan 2026 10:51:58 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <547218.1769530268.1@sss.pgh.pa.us>
Date: Tue, 27 Jan 2026 11:11:08 -0500
Message-ID: <547219.1769530268@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/547219.1769530268%40sss.pgh.pa.us>
Precedence: bulk

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