database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Add note in pg_stat_statements documentation about planning statistics.

Browse Source 
The added note explains that the numbers of planning and execution in
the statement are not always expected to match because their statistics are
updated at their respective end phase, and only for successful operations.

Author: Pascal Legrand, Julien Rouhaud, tweaked a bit by Fujii Masao
Discussion: https://postgr.es/m/1585857868967-0.post@n3.nabble.com
This commit is contained in:
Fujii Masao 2020-04-09 12:56:36 +09:00
parent c3e4cbaab9
commit 58ad961f19
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/pgstatstatements.sgml
View File

@ -129,7 +129,7 @@
<entry><structfield>calls</structfield></entry> <entry><structfield>calls</structfield></entry>
<entry><type>bigint</type></entry> <entry><type>bigint</type></entry>
<entry></entry> <entry></entry>
<entry>Number of times executed</entry> <entry>Number of times the statement was executed</entry>
</row> </row>
<row> <row>
@ -398,6 +398,16 @@
reducing <varname>pg_stat_statements.max</varname> to prevent reducing <varname>pg_stat_statements.max</varname> to prevent
recurrences. recurrences.
</para> </para>
<para>
<structfield>plans</structfield> and <structfield>calls</structfield> aren't
always expected to match because planning and execution statistics are
updated at their respective end phase, and only for successful operations.
For example, if a statement is successfully planned but fails during
the execution phase, only its planning statistics will be updated.
If planning is skipped because a cached plan is used, only its execution
statistics will be updated.
</para>
</sect2> </sect2>
<sect2> <sect2>