| commit | 5fd9dfa5f50e4906c35133a414ebec5b6d518493 | |
| author | Bruce Momjian <bruce@momjian.us> | |
| Wed, 7 Apr 2021 17:06:47 +0000 (7 13:06 -0400) | ||
| committer | Bruce Momjian <bruce@momjian.us> | |
| Wed, 7 Apr 2021 17:06:56 +0000 (7 13:06 -0400) | ||
| tree | 4bf0c6c9088eb8b053b029b9be787939d48d2e3b | treesnapshot (tar.gz zip) |
| parent | a282ee68a070a8adc6e6d45e8e643769c587ecc3 | commitdiff |
Move pg_stat_statements query jumbling to core.
Add compute_query_id GUC to control whether a query identifier should be
computed by the core (off by default). It's thefore now possible to
disable core queryid computation and use pg_stat_statements with a
different algorithm to compute the query identifier by using a
third-party module.
To ensure that a single source of query identifier can be used and is
well defined, modules that calculate a query identifier should throw an
error if compute_query_id specified to compute a query id and if a query
idenfitier was already calculated.
Discussion: https://postgr.es/m/20210407125726.tkvjdbw76hxnpwfi@nol
Author: Julien Rouhaud
Reviewed-by: Alvaro Herrera, Nitin Jadhav, Zhihong Yu
Add compute_query_id GUC to control whether a query identifier should be
computed by the core (off by default). It's thefore now possible to
disable core queryid computation and use pg_stat_statements with a
different algorithm to compute the query identifier by using a
third-party module.
To ensure that a single source of query identifier can be used and is
well defined, modules that calculate a query identifier should throw an
error if compute_query_id specified to compute a query id and if a query
idenfitier was already calculated.
Discussion: https://postgr.es/m/20210407125726.tkvjdbw76hxnpwfi@nol
Author: Julien Rouhaud
Reviewed-by: Alvaro Herrera, Nitin Jadhav, Zhihong Yu
13 files changed: