pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Improve log messages and docs for slot synchronization. 2+ messages / 1 participants [nested] [flat]
* pgsql: Improve log messages and docs for slot synchronization. @ 2025-06-19 04:40 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Amit Kapila @ 2025-06-19 04:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Improve log messages and docs for slot synchronization. @ 2025-06-19 04:40 Amit Kapila <akapila@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Amit Kapila @ 2025-06-19 04:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/25505082f0e7aa6dc9cd068b0e5330bb1ca22751 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(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-06-19 04:40 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-06-19 04:40 pgsql: Improve log messages and docs for slot synchronization. Amit Kapila <akapila@postgresql.org> 2025-06-19 04:40 pgsql: Improve log messages and docs for slot synchronization. Amit Kapila <akapila@postgresql.org>
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