pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alexander Korotkov <akorotkov@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Keep WAL segments by the flushed value of the slot's restart LSN
Date: Sat, 14 Jun 2025 01:29:26 +0000
Message-ID: <E1uQFi2-001YDc-1f@gemulon.postgresql.org> (raw)

Keep WAL segments by the flushed value of the slot's restart LSN

The patch fixes the issue with the unexpected removal of old WAL segments
after checkpoint, followed by an immediate restart.  The issue occurs when
a slot is advanced after the start of the checkpoint and before old WAL
segments are removed at the end of the checkpoint.

The idea of the patch is to get the minimal restart_lsn at the beginning
of checkpoint (or restart point) creation and use this value when calculating
the oldest LSN for WAL segments removal at the end of checkpoint.  This idea
was proposed by Tomas Vondra in the discussion.  Unlike 291221c46575, this
fix doesn't affect ABI and is intended for back branches.

Discussion: https://postgr.es/m/flat/1d12d2-67235980-35-19a406a0%4063439497
Author: Vitaly Davydov <v.davydov@postgrespro.ru>
Reviewed-by: Tomas Vondra <tomas@vondra.me>
Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Backpatch-through: 13

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/cea8f2c3e44b5fac59a7298c6b9045c5cbb0eaeb

Modified Files
--------------
src/backend/access/transam/xlog.c         | 55 ++++++++++++++++++++++++++-----
src/backend/replication/logical/logical.c | 10 +++++-
src/backend/replication/walsender.c       |  4 +++
3 files changed, 60 insertions(+), 9 deletions(-)



view thread (5+ messages)  latest in thread

Message-ID: <E1uQFi2-001YDc-1f@gemulon.postgresql.org>
Permalink:  ../E1uQFi2-001YDc-1f@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1uQFi2-001YDc-1f@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: akorotkov@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Keep WAL segments by the flushed value of the slot's restart LSN
  In-Reply-To: <E1uQFi2-001YDc-1f@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