Re: Redact user password on pg_stat_statements

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Redact user password on pg_stat_statements
Date: 2025-02-25 13:46:46
Message-ID: CAKAnmmK+1nXEJNzh8tRYHjzHXzP=LHDryLbtMa8tpWexAg7uAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

What about a more general solution, such as a flag to turn off logging of
ALTER ROLE statements completely? Does anyone really need to know the
standard deviation of the timings for "ALTER ROLE alice SET
work_mem='50MB'"? Let's be honest, there are a lot of things that go into
pg_stat_statements that don't need to. Removing ALTER ROLE entirely would
have a bonus security side-effect, without it being the primary driver.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2025-02-25 14:18:40 Re: [PATCH] Refactor SLRU to always use long file names
Previous Message Bertrand Drouvot 2025-02-25 13:42:08 [BUG]: the walsender does not update its IO statistics until it exits