Re: compute_query_id and pg_stat_statements
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Magnus Hagander <magnus@hagander.net>, Bruce Momjian <bruce@momjian.us>,
Christoph Berg <myon@debian.org>,
Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Fujii Masao <masao.fujii@oss.nttdata.com>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-26T17:29:00Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: > * Magnus Hagander (magnus@hagander.net) wrote: >> Thatäs why I suggested the three value one. Default to a mode where >> it's automatic, which is what the majority is going to want, but have >> a way to explicitly turn it on. > This is certainly fine with me too, though it seems a bit surprising to > me that we couldn't just figure out what the user actually wants based > on what's installed/running for any given combination. I'd be on board with having pg_stat_statement's pg_init function do something to adjust the setting, if we can figure out how to do that in a way that's not confusing in itself. I'm not sure though that the GUC engine offers a good way. regards, tom lane
Commits
-
Allow compute_query_id to be set to 'auto' and make it default
- cafde58b337e 14.0 landed
-
Move pg_stat_statements query jumbling to core.
- 5fd9dfa5f50e 14.0 cited