postgres

History

Michael Paquier de2aca2885 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		3 years ago
..
cleanup.sql	Refactor tests of pg_stat_statements for planning, utility and level tracking	3 years ago
cursors.sql	Expand regression tests of pg_stat_statements for utility queries	3 years ago
level_tracking.sql	Refactor tests of pg_stat_statements for planning, utility and level tracking	3 years ago
oldextversions.sql	pg_stat_statements: Track I/O timing for temporary file blocks	3 years ago
pg_stat_statements.sql	Refactor tests of pg_stat_statements for planning, utility and level tracking	3 years ago
planning.sql	Refactor tests of pg_stat_statements for planning, utility and level tracking	3 years ago
utility.sql	Expand regression tests of pg_stat_statements for utility queries	3 years ago