From 7531fcb1fcf5b3ea2f49959a3f095c083e3fc4c4 Mon Sep 17 00:00:00 2001 From: Magnus Hagander Date: Fri, 23 Apr 2021 11:41:36 +0200 Subject: [PATCH] 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 --- doc/src/sgml/pgstatstatements.sgml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml index a0c315aa97..bc2b6038ee 100644 --- a/doc/src/sgml/pgstatstatements.sgml +++ b/doc/src/sgml/pgstatstatements.sgml @@ -46,8 +46,8 @@ The statistics gathered by the module are made available via a view named pg_stat_statements. 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 . @@ -93,6 +93,8 @@ True if the query was executed as a top level statement + (if pg_stat_statements.track is set to + all, otherwise always false)