Horton

Re: compute_query_id and pg_stat_statements

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Magnus Hagander <magnus@hagander.net>, Fujii Masao <masao.fujii@oss.nttdata.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-24T17:43:51Z
Lists: pgsql-hackers 
Bruce Momjian <bruce@momjian.us> writes:
> That's a pretty weird API.  I think we just need people to turn it on
> like they are doing when the configure pg_stat_statements anyway. 
> pg_stat_statements already requires configuration anyway.

Agreed.  If pg_stat_statements were zero-configuration today then
this would be an annoying new burden, but it isn't.

I haven't looked, but did we put anything into pg_stat_statements
to make it easy to tell if you've messed up this setting?

			regards, tom lane

Commits

  1. Allow compute_query_id to be set to 'auto' and make it default

  2. Move pg_stat_statements query jumbling to core.