Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 6a88a05

Browse files
committed
doc: Update pg_stat_statements about query ID calculation of utilities
Since 3db72eb, the calculation of the query ID hash for utilities is not done based on the textual query strings, but on their internal Query representation, meaning that there can be an overlap when they use literal constants. The documentation of pg_stat_statements was missing a refresh about that. Extracted from a larger patch by me. Discussion: https://postgr.es/m/Y+MRdEq9W9XVa2AB@paquier.xyz
1 parent b1b8682 commit 6a88a05

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/sgml/pgstatstatements.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -487,13 +487,13 @@
487487

488488
<para>
489489
Plannable queries (that is, <command>SELECT</command>, <command>INSERT</command>,
490-
<command>UPDATE</command>, <command>DELETE</command>, and <command>MERGE</command>) are combined into a single
490+
<command>UPDATE</command>, <command>DELETE</command>, and <command>MERGE</command>)
491+
and utility commands are combined into a single
491492
<structname>pg_stat_statements</structname> entry whenever they have identical query
492493
structures according to an internal hash calculation. Typically, two
493494
queries will be considered the same for this purpose if they are
494495
semantically equivalent except for the values of literal constants
495-
appearing in the query. Utility commands (that is, all other commands)
496-
are compared strictly on the basis of their textual query strings, however.
496+
appearing in the query.
497497
</para>
498498

499499
<note>

0 commit comments

Comments
 (0)