Re: allow online change primary_conninfo - Mailing list pgsql-hackers

From Sergei Kornilov
Subject Re: allow online change primary_conninfo
Date
Msg-id 6789441548940402@sas1-fb8a605c4548.qloud-c.yandex.net
Whole thread Raw
In response to Re: allow online change primary_conninfo  ("andres@anarazel.de" <andres@anarazel.de>)
Responses Re: allow online change primary_conninfo  (Michael Paquier <michael@paquier.xyz>)
Re: allow online change primary_conninfo  ("andres@anarazel.de" <andres@anarazel.de>)
List pgsql-hackers
Hello

Yeah, we have no consensus.

Another open question is about logging new primary_conninfo:

> LOG: parameter "primary_conninfo" changed to "host=/tmp port=5432 password=hoge"

I my opinion this is not issue, database logs can have sensitive data. User queries, for example.
If we not want expose such info - it is ok just hide new value from logs with new GUC flag? Or i need implement masked
conninfofor this purpose?
 

regards, Sergei


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: bug tracking system
Next
From: Andres Freund
Date:
Subject: Re: Add --include-table-data-where option to pg_dump, to export onlya subset of table data