Mention that toplevel is part of pg_stat_statements key.

While at it, also document that toplevel is always true if
pg_stat_statements.track is set to top.

Author: Julien Rouhaud
Reported-By: Fujii Masao
Discussion: https://postgr.es/m/a878d5ea-64a7-485e-5d2f-177618ebc52d@oss.nttdata.com
This commit is contained in:
Magnus Hagander 2021-04-23 11:41:36 +02:00
parent add5fad78a
commit 7531fcb1fc
1 changed files with 4 additions and 2 deletions

View File

@ -46,8 +46,8 @@
<para>
The statistics gathered by the module are made available via a
view named <structname>pg_stat_statements</structname>. This view
contains one row for each distinct database ID, user ID and query
ID (up to the maximum number of distinct statements that the module
contains one row for each distinct database ID, user ID, query ID and
toplevel (up to the maximum number of distinct statements that the module
can track). The columns of the view are shown in
<xref linkend="pgstatstatements-columns"/>.
</para>
@ -93,6 +93,8 @@
</para>
<para>
True if the query was executed as a top level statement
(if <varname>pg_stat_statements.track</varname> is set to
<literal>all</literal>, otherwise always false)
</para></entry>
</row>