| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | "andres(at)anarazel(dot)de" <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow online change primary_conninfo |
| Date: | 2019-01-31 13:13:22 |
| Message-ID: | 6789441548940402@sas1-fb8a605c4548.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 conninfo for this purpose?
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-01-31 13:21:08 | Re: Add --include-table-data-where option to pg_dump, to export only a subset of table data |
| Previous Message | Alvaro Herrera | 2019-01-31 13:02:57 | Re: bug tracking system |