diff options
Diffstat (limited to '')
| -rw-r--r-- | doc/src/sgml/pgstatstatements.sgml | 24 |
1 files changed, 15 insertions, 9 deletions
diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml index ea90365..c8aa43a 100644 --- a/doc/src/sgml/pgstatstatements.sgml +++ b/doc/src/sgml/pgstatstatements.sgml @@ -554,15 +554,21 @@ </para> <para> - As a rule of thumb, <structfield>queryid</structfield> 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 <structfield>queryid</structfield> values for the same query. - However, logical replication schemes do not promise to keep replicas - identical in all relevant details, so <structfield>queryid</structfield> 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 <structfield>queryid</structfield> values for + the same query. However, logical replication schemes do not promise to + keep replicas identical in all relevant details, so + <structfield>queryid</structfield> will not be a useful identifier for + accumulating costs across a set of logical replicas. + If in doubt, direct testing is recommended. + </para> + + <para> + Generally, it can be assumed that <structfield>queryid</structfield> values + are stable between minor version releases of <productname>PostgreSQL</productname>, + 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. </para> <para> |