Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Date
Msg-id 20210323151203.GA8662@alvherre.pgsql
Whole thread Raw
In response to Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 2021-Mar-22, Bruce Momjian wrote:

> --- a/doc/src/sgml/ref/explain.sgml
> +++ b/doc/src/sgml/ref/explain.sgml
> @@ -136,8 +136,10 @@ ROLLBACK;
>        the output column list for each node in the plan tree, schema-qualify
>        table and function names, always label variables in expressions with
>        their range table alias, and always print the name of each trigger for
> -      which statistics are displayed.  This parameter defaults to
> -      <literal>FALSE</literal>.
> +      which statistics are displayed.  The query identifier will also be
> +      displayed if one has been compute, see <xref
> +      linkend="guc-compute-query-id"/> for more details.  This parameter
> +      defaults to <literal>FALSE</literal>.

Typo here, "has been computed".

Is the intention to commit each of these patches separately?

-- 
Álvaro Herrera       Valdivia, Chile



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: Support ALTER SUBSCRIPTION ... ADD/DROP PUBLICATION ... syntax
Next
From: Masahiko Sawada
Date:
Subject: Re: 64-bit XIDs in deleted nbtree pages