Improve logical replication connection-failure messages.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 11 Jul 2024 17:21:13 +0000 (13:21 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 11 Jul 2024 17:21:13 +0000 (13:21 -0400)
commit0d8bd0a72ea284ffb1d1154efbe799241cc5edc6
treea02394fd7eede77c17ed5ae77996202339c39cc4
parenta0f1fce80c0373c16b22a1bdc9b0b61958fc9b6a
Improve logical replication connection-failure messages.

These messages mostly said "could not connect to the publisher: %s"
which is lacking context.  Add some verbiage to indicate which
subscription or worker process is failing.

Nisha Moond

Discussion: http://postgr.es/m/CABdArM7q1=zqL++cYd0hVMg3u_tc0S=0Of=Um-KvDhLony0cSg@mail.gmail.com
src/backend/commands/subscriptioncmds.c
src/backend/replication/logical/slotsync.c
src/backend/replication/logical/tablesync.c
src/backend/replication/logical/worker.c
src/backend/replication/slotfuncs.c
src/backend/replication/walreceiver.c
src/test/regress/expected/subscription.out