On Sat, May 15, 2021 at 07:01:25PM -0400, Álvaro Herrera wrote:
> On 2021-May-15, Bruce Momjian wrote:
>
> > On Sat, May 15, 2021 at 02:21:59PM -0400, Álvaro Herrera wrote:
>
> > > I wonder why the initial line says "query hash" instead of "query
> > > identifier". Do we want to say "hash" everywhere? Why didn't we name
> > > the GUC "compute_query_hash" in that case?
> >
> > It is queryid (no underscore) in pg_stat_statements, which was a whole
> > different discussion. ;-)
>
> Yeah, I realize that, but I wonder if we shouldn't use the term "query
> identifier" instead of "query hash" in that paragraph.
Yes, of course, you are right --- updated text:
<listitem>
<!--
Author: Bruce Momjian <bruce@momjian.us>
2021-04-07 [4f0b0966c] Make use of in-core query id added by commit 5fd9dfa5f5
Author: Bruce Momjian <bruce@momjian.us>
2021-04-07 [f57a2f5e0] Add csvlog output for the new query_id value
Author: Bruce Momjian <bruce@momjian.us>
2021-04-20 [9660834dd] adjust query id feature to use pg_stat_activity.query_id
Author: Bruce Momjian <bruce@momjian.us>
2021-05-03 [f7a97b6ec] Update query_id computation
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
2021-05-15 [cafde58b3] Allow compute_query_id to be set to 'auto' and make it d
-->
<para>
If server variable compute_query_id is enabled, display the query
id in pg_stat_activity, EXPLAIN VERBOSE, csvlog, and optionally
in log_line_prefix (Julien Rouhaud)
</para>
<para>
A query id computed by an extension will also be displayed.
</para>
</listitem>
>
> > I also added Alvaro as an author of the compute_query_id item.
>
> I've been wondering if I should ask to stick my name in other features I
> helped get committed -- specifically the PQtrace() item and autovacuum
> for partitioned tables. I'll go comment in the release notes thread.
Yes, done.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
