aboutsummaryrefslogtreecommitdiff
path: root/contrib/pageinspect/gistfuncs.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2022-03-04 14:49:37 +0100
committerPeter Eisentraut <peter@eisentraut.org>2022-03-07 08:13:30 +0100
commit25751f54b8e02a8fff62e9dbdbc9f2efbb4e8dc1 (patch)
tree6de17d8744ac53b5b786a9427c83bf201b8df50b /contrib/pageinspect/gistfuncs.c
parent5e0e99a80b2f41c8e9ed0f4071892d9e797a12be (diff)
downloadpostgresql-25751f54b8e02a8fff62e9dbdbc9f2efbb4e8dc1.tar.gz
postgresql-25751f54b8e02a8fff62e9dbdbc9f2efbb4e8dc1.zip
Add pg_analyze_and_rewrite_varparams()
This new function extracts common code from PrepareQuery() and exec_parse_message(). It is then exactly analogous to the existing pg_analyze_and_rewrite_fixedparams() and pg_analyze_and_rewrite_withcb(). To unify these two code paths, this makes PrepareQuery() now subject to log_parser_stats. Also, both paths now invoke TRACE_POSTGRESQL_QUERY_REWRITE_START(). PrepareQuery() no longer checks whether a utility statement was specified. The grammar doesn't allow that anyway, and exec_parse_message() supports it, so restricting it doesn't seem necessary. This also adds QueryEnvironment support to the *varparams functions, for consistency with its cousins, even though it is not used right now. Reviewed-by: Nathan Bossart <bossartn@amazon.com> Discussion: https://www.postgresql.org/message-id/flat/c67ce276-52b4-0239-dc0e-39875bf81840@enterprisedb.com
Diffstat (limited to 'contrib/pageinspect/gistfuncs.c')
0 files changed, 0 insertions, 0 deletions