On Tue, Mar 25, 2025, 6:28 PM Álvaro Herrera <alvherre@alvh.no-ip.org> wrote:On 2025-Mar-25, Tom Lane wrote:> If this GUC sticks around, it should be at least PGC_SUSET (on> the analogy of compute_query_id) to make it harder to break> pg_stat_statements that way.I have no problem making it superuser-only, and I can see making "on" bethe default. I am not opposed to removing it completely either, if wereally think that the current behavior is no longer useful for anybody.I'm in favor of removing the GUC of course, but if memory serves therewere some folks in the patch discussion thread, who claimed they wouldneed to be able to keep non-squashed behavior. I don't recall if there wereparticular arguments to support that, will try to find those messages again.
On Tue, Mar 25, 2025, 6:28 PM Álvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2025-Mar-25, Tom Lane wrote:
> If this GUC sticks around, it should be at least PGC_SUSET (on
> the analogy of compute_query_id) to make it harder to break
> pg_stat_statements that way.
I have no problem making it superuser-only, and I can see making "on" be
the default. I am not opposed to removing it completely either, if we
really think that the current behavior is no longer useful for anybody.
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных