pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <fujii@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Stabilize 019_replslot_limit
Date: Thu, 27 Aug 2026 14:59:03 +0000
Message-ID: <E1wzbZG-00000002M63-0QEK@gemulon.postgresql.org> (raw)

Stabilize 019_replslot_limit

The test assumed that advancing WAL would lead to a checkpoint that
invalidates the obsolete replication slot.  If a checkpoint that started
before the WAL switch completes first, the following checkpoint can be
skipped as idle, so the expected walsender termination is not logged.

Force a CHECKPOINT in a background psql session after advancing WAL, so
the slot invalidation is exercised deterministically.

This has been observed on buildfarm members alligator and partridge:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2024-12-13%2001%3A24%3A58
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=partridge&dt=2026-08-06%2018%3A00%3A11

Backpatch to all supported versions.

Reported-by: Alexander Lakhin <exclusion@gmail.com>
Author: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Reviewed-by: Alexander Lakhin <exclusion@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Discussion: https://postgr.es/m/0b07ead5-a5da-445e-9698-a7d340708bdf@gmail.com
Backpatch-through: 14

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/11c4bc621ae7cf27f00b95d0cf04e7a995c3dbe9

Modified Files
--------------
src/test/recovery/t/019_replslot_limit.pl | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)



view thread (7+ messages)  latest in thread

Message-ID: <E1wzbZG-00000002M63-0QEK@gemulon.postgresql.org>
Permalink:  ../E1wzbZG-00000002M63-0QEK@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1wzbZG-00000002M63-0QEK@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: fujii@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Stabilize 019_replslot_limit
  In-Reply-To: <E1wzbZG-00000002M63-0QEK@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox