database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

doc: Update pg_stat_statements about query ID calculation of utilities

Browse Source 
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
This commit is contained in:
Michael Paquier
2023-03-01 10:31:55 +09:00
parent b1b86820d8
commit 6a88a05861
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

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