From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/pgstatstatements.html | 26 +++++++++++++++----------- 1 file changed, 15 insertions(+), 11 deletions(-) (limited to 'doc/src/sgml/html/pgstatstatements.html') diff --git a/doc/src/sgml/html/pgstatstatements.html b/doc/src/sgml/html/pgstatstatements.html index 5a45f07..fac38c0 100644 --- a/doc/src/sgml/html/pgstatstatements.html +++ b/doc/src/sgml/html/pgstatstatements.html @@ -1,5 +1,5 @@ -F.32. pg_stat_statements
F.32. pg_stat_statements
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.32. pg_stat_statements

F.32.1. The pg_stat_statements View
F.32.2. The pg_stat_statements_info View
F.32.3. Functions
F.32.4. Configuration Parameters
F.32.5. Sample Output
F.32.6. Authors

+F.32. pg_stat_statements

F.32. pg_stat_statements
Prev UpAppendix F. Additional Supplied ModulesHome Next

F.32. pg_stat_statements

F.32.1. The pg_stat_statements View
F.32.2. The pg_stat_statements_info View
F.32.3. Functions
F.32.4. Configuration Parameters
F.32.5. Sample Output
F.32.6. Authors

The pg_stat_statements module provides a means for tracking planning and execution statistics of all SQL statements executed by a server. @@ -333,15 +333,19 @@ Furthermore, it is not safe to assume that queryid will be stable across major versions of PostgreSQL.

- As a rule of thumb, queryid values can be assumed to be - stable and comparable only so long as the underlying server version and - catalog metadata details stay exactly the same. Two servers - participating in replication based on physical WAL replay can be expected - to have identical queryid values for the same query. - However, logical replication schemes do not promise to keep replicas - identical in all relevant details, so queryid will - not be a useful identifier for accumulating costs across a set of logical - replicas. If in doubt, direct testing is recommended. + Two servers participating in replication based on physical WAL replay can + be expected to have identical queryid values for + the same query. However, logical replication schemes do not promise to + keep replicas identical in all relevant details, so + queryid will not be a useful identifier for + accumulating costs across a set of logical replicas. + If in doubt, direct testing is recommended. +

+ Generally, it can be assumed that queryid values + are stable between minor version releases of PostgreSQL, + providing that instances are running on the same machine architecture and + the catalog metadata details match. Compatibility will only be broken + between minor versions as a last resort.

The parameter symbols used to replace constants in representative query texts start from the next number after the @@ -610,4 +614,4 @@ hit_percent |

F.32.6. Authors

Takahiro Itagaki . Query normalization added by Peter Geoghegan . -

Prev Up Next
F.31. pgrowlocks Home F.33. pgstattuple
\ No newline at end of file +

Prev Up Next
F.31. pgrowlocks Home F.33. pgstattuple
\ No newline at end of file -- cgit v1.2.3