Re: Redact user password on pg_stat_statements
От | Sami Imseih |
---|---|
Тема | Re: Redact user password on pg_stat_statements |
Дата | |
Msg-id | CAA5RZ0uFdOeAOJaSsGym5bk3mxQMKk=RLpkTbwNbTbkC29cVKw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Redact user password on pg_stat_statements (Greg Sabino Mullane <htamfids@gmail.com>) |
Ответы |
Re: Redact user password on pg_stat_statements
Re: Redact user password on pg_stat_statements |
Список | pgsql-hackers |
> What about a more general solution, such as a flag to turn off logging of ALTER ROLE statements completely? IMO, flags for a specific type of utility statement seems way too much for pg_stat_statements, and this will also not completely prevent leaking plain text passwords from all ways that CREATE/ALTER ROLE could be run, i.e. DO blocks, inside functions/procs with track=all. The clients that set passwords could simply turn off track_utility on a user/transaction level while they are performing the action with sensitive data. -- Sami Amazon Web Services (AWS)
В списке pgsql-hackers по дате отправления: