pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Amit Kapila <akapila@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Improve log messages and docs for slot synchronization.
Date: Thu, 19 Jun 2025 04:40:55 +0000
Message-ID: <E1uS755-002MFm-22@gemulon.postgresql.org> (raw)

Improve log messages and docs for slot synchronization.

Improve the clarity of LOG messages when a failover logical slot
synchronization fails, making the reasons more explicit for easier
debugging.

Update the documentation to outline scenarios where slot synchronization
can fail, especially during the initial sync, and emphasize that
pg_sync_replication_slot() is primarily intended for testing and
debugging purposes.

We also discussed improving the functionality of
pg_sync_replication_slot() so that it can be used reliably, but we would
take up that work for next version after some more discussion and review.

Reported-by: Suraj Kharage <suraj.kharage@enterprisedb.com>
Author: shveta malik <shveta.malik@gmail.com>
Reviewed-by: Zhijie Hou <houzj.fnst@fujitsu.com>
Reviewed-by: Peter Smith <smithpb2250@gmail.com>
Reviewed-by: Amit Kapila <amit.kapila16@gmail.com>
Backpatch-through: 17, where it was introduced
Discussion: https://postgr.es/m/CAF1DzPWTcg+m+x+oVVB=y4q9=PYYsL_mujVp7uJr-_oUtWNGbA@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1546e17f9d067e714e066fcdd57d5f56c14f4174

Modified Files
--------------
doc/src/sgml/func.sgml                     |  6 ++--
doc/src/sgml/logicaldecoding.sgml          | 54 +++++++++++++++++++++++++++---
src/backend/replication/logical/slotsync.c |  6 ++--
3 files changed, 57 insertions(+), 9 deletions(-)



view thread (2+ messages)  latest in thread

Message-ID: <E1uS755-002MFm-22@gemulon.postgresql.org>
Permalink:  ../E1uS755-002MFm-22@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1uS755-002MFm-22@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: akapila@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Improve log messages and docs for slot synchronization.
  In-Reply-To: <E1uS755-002MFm-22@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