Re: compute_query_id and pg_stat_statements
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>,
Christoph Berg <myon@debian.org>, Julien Rouhaud <rjuju123@gmail.com>,
Pavel Stehule <pavel.stehule@gmail.com>,
Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
Magnus Hagander <magnus@hagander.net>,
Fujii Masao <masao.fujii@oss.nttdata.com>,
Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>,
Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-13T23:19:11Z
Lists: pgsql-hackers
On 5/13/21 3:04 PM, Alvaro Herrera wrote: > On 2021-May-13, Stephen Frost wrote: > >> Or just accept that this is a bit hokey with the 'auto' approach. I get >> Bruce has concerns about it but I'm not convinced that it's actually all >> that bad to go with that. > Yeah, I think the alleged confusion there is overstated. > > I'm happy to act as committer for that if he wants to step away from it. > I'm already used to being lapidated at every corner anyway. > Many thanks Alvaro, among other things for teaching me a new word. cheers (delapidated) andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
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