aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2022-02-22 10:22:15 +0900
committerMichael Paquier <michael@paquier.xyz>2022-02-22 10:22:15 +0900
commitebf6c5249b7db525e59563fb149642665c88f747 (patch)
treedd6c915361709ca1c7009f3af3fed2e9dc05b9d4 /src/backend/access/gist/gistbuild.c
parent88103567cb8fa5be46dc9fac3e3b8774951a2be7 (diff)
downloadpostgresql-ebf6c5249b7db525e59563fb149642665c88f747.tar.gz
postgresql-ebf6c5249b7db525e59563fb149642665c88f747.zip
Add compute_query_id = regress
"regress" is a new mode added to compute_query_id aimed at facilitating regression testing when a module computing query IDs is loaded into the backend, like pg_stat_statements. It works the same way as "auto", meaning that query IDs are computed if a module enables it, except that query IDs are hidden in EXPLAIN outputs to ensure regression output stability. Like any GUCs of the kind (force_parallel_mode, etc.), this new configuration can be added to an instance's postgresql.conf, or just passed down with PGOPTIONS at command level. compute_query_id uses an enum for its set of option values, meaning that this addition ensures ABI compatibility. Using this new configuration mode allows installcheck-world to pass when running the tests on an instance with pg_stat_statements enabled, stabilizing the test output while checking the paths doing query ID computations. Reported-by: Anton Melnikov Reviewed-by: Julien Rouhaud Discussion: https://postgr.es/m/1634283396.372373993@f75.i.mail.ru Discussion: https://postgr.es/m/YgHlxgc/OimuPYhH@paquier.xyz Backpatch-through: 14
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions