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 1ca19c1a7a8871d81ceff133974ab92478025adc..2548d3feb54f28c379a956e7c25300b180316a67 100644 (file)
--- a/src/backend/replication/logical/worker.c
+++ b/src/backend/replication/logical/worker.c
@@ -6003,10 +6003,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.