Horton

Re: compute_query_id and pg_stat_statements

Pavel Stehule <pavel.stehule@gmail.com>

View thread View on postgr.es
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>, Magnus Hagander <magnus@hagander.net>, Fujii Masao <masao.fujii@oss.nttdata.com>, Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Stephen Frost <sfrost@snowman.net>, Bruce Momjian <bruce@momjian.us>, Christoph Berg <myon@debian.org>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-12T05:49:13Z
Lists: pgsql-hackers 
Hi


> Ah, I missed that case.  And we are wanting to use pg_stat_statements
> with (almost) zero-config?  How about the following behavior?
>
>
Until now, the pg_stat_statements was zero-config. So the change is not
user friendly.

The idea so pg_stat_statements requires enabled computed_query_id is not
good. There should be dependency only on the queryid column.

Regards

Pavel

Commits

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

  2. Move pg_stat_statements query jumbling to core.