Open
Description
If spock subscription is created( DSN containing password )then on error like connection breakage, subscription information contains the DSN which contains the password also causing security compliance issue. It would be good to obfuscate the password in such situation on printing errors.
Below is logs (removed identifiers):
25-06-10 04:01:30.939 UTC [44] LOG: background worker "spock apply 16386:1248781941" (PID 734) exited with exit code 1
2025-06-10 04:01:35.949 UTC [840] ERROR: could not connect to the postgresql server in replication mode: connection to server at "X.Y.Z.K", port 5433 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?
2025-06-10 04:01:35.949 UTC [840] DETAIL: dsn was: host=XXXX port=XXXX user=XXXX dbname=XXX password=XXXX
2025-06-10 04:01:35.949 UTC [840] LOG: apply worker [840] at slot 1 generation 44 exiting with error
2025-06-10 04:01:35.953 UTC [44] LOG: background worker "spock apply 16386:1248781941" (PID 840) exited with exit code 1
Metadata
Metadata
Assignees
Labels
No labels