aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-01-26 12:23:16 +0900
committerMichael Paquier <michael@paquier.xyz>2023-01-26 12:23:16 +0900
commit9d2d9728b8d546434aade4f9667a59666588edd6 (patch)
treef708188532e0d0cc85cbe5f03d892edce07478ee /contrib/postgres_fdw/postgres_fdw.c
parentffcf6f4cfca5a4ce2ac7ff7e8fa17541a5a9caea (diff)
downloadpostgresql-9d2d9728b8d546434aade4f9667a59666588edd6.tar.gz
postgresql-9d2d9728b8d546434aade4f9667a59666588edd6.zip
Make auto_explain print the query identifier in verbose mode
When auto_explain.log_verbose is on, auto_explain should print in the logs plans equivalent to the EXPLAIN (VERBOSE). However, when compute_query_id is on, query identifiers were not showing up, being only handled by EXPLAIN (VERBOSE). This brings auto_explain on par with EXPLAIN regarding that. Note that like EXPLAIN, auto_explain does not show the query identifier when compute_query_id=regress. The change is done so as the choice of printing the query identifier is done in ExplainPrintPlan() rather than in ExplainOnePlan(), to avoid a duplication of the logic dealing with the query ID. auto_explain is the only in-core caller of ExplainPrintPlan(). While looking at the area, I have noticed that more consolidation between EXPLAIN and auto_explain would be in order for the logging of the plan duration and the buffer usage. This refactoring is left as a future change. Author: Atsushi Torikoshi Reviewed-by: Justin Pryzby, Julien Rouhaud Discussion: https://postgr.es/m/1ea21936981f161bccfce05765c03bee@oss.nttdata.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions