aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-02-20 10:16:51 +0900
committerMichael Paquier <michael@paquier.xyz>2023-02-20 10:16:51 +0900
commitde2aca288569fd0cabb425c0858e92e2c8c938cb (patch)
tree3080425ca66229a23f25edd485132b2870a65591 /src/backend/tcop/postgres.c
parente8dbdb15dbc8529518ab0303bf358d07c7ad9e18 (diff)
downloadpostgresql-de2aca288569fd0cabb425c0858e92e2c8c938cb.tar.gz
postgresql-de2aca288569fd0cabb425c0858e92e2c8c938cb.zip
Expand regression tests of pg_stat_statements for utility queries
This commit adds more coverage for utility statements so as it is possible to track down all the effects of query normalization done for all the queries that use either Const or A_Const nodes, which are the nodes where normalization makes the most sense as they apply to constants (well, most of the time, really). This set of queries is extracted from an analysis done while looking at full dumps of the regression database when applying different levels of normalization to either Const or A_Const nodes for utilities, as of a minimal set of these, for: - All relkinds (CREATE, ALTER, DROP) - Policies - Cursors - Triggers - Types - Rules - Statistics - CALL - Transaction statements (isolation level, options) - EXPLAIN - COPY Note that pg_stat_statements is not switched yet to show any normalization for utilities, still it improves the default coverage of the query jumbling code (not by as much as enabling query jumbling on the main regression test suite, though): - queryjumblefuncs.funcs.c: 36.8% => 48.5% - queryjumblefuncs.switch.c: 33.2% => 43.1% Reviewed-by: Bertrand Drouvot Discussion: https://postgr.es/m/Y+MRdEq9W9XVa2AB@paquier.xyz
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions