Do not log subscription conninfo.

Logging connection information, even at DEBUG1, creates unnecessary
risks. Remove the entire log message because it had no other useful
content.

Addresses finding 14 in report from linked discussion.

Reported-by: Noah Misch <noah@leadboat.com>
Discussion: https://postgr.es/m/20260710195902.4f.noahmisch@microsoft.com
Backpatch-through: 14

diff --git a/src/backend/replication/logical/worker.c b/src/backend/replication/logical/worker.c
index 3c4a0b907a46ed2f533216f29d8cf7bcd0b7be41..24ce03be0673df59a91eaa72be11baee92b07fd3 100644 (file)
--- a/src/backend/replication/logical/worker.c
+++ b/src/backend/replication/logical/worker.c
@@ -5995,10 +5995,6 @@ SetupApplyOrSyncWorker(int worker_slot)
 
        InitializeLogRepWorker();
 
-       /* Connect to the origin and start the replication. */
-       elog(DEBUG1, "connecting to publisher using connection string \"%s\"",
-                MySubscription->conninfo);
-
        /*
         * Setup callback for syscache so that we know when something changes in
         * the subscription relation state.