diff options
| author | Michael Paquier <michael@paquier.xyz> | 2024-03-11 08:40:40 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2024-03-11 08:40:40 +0900 |
| commit | a04ddd077e61096da660e1c2f205e0c8277f2dcd (patch) | |
| tree | bfe3bdf4f135343cd1c3cd074737b972038942d1 /src/backend/executor/nodeMemoize.c | |
| parent | c399248b3b44bd6cece1ada47eee346b67a88a0a (diff) | |
| download | postgresql-a04ddd077e61096da660e1c2f205e0c8277f2dcd.tar.gz postgresql-a04ddd077e61096da660e1c2f205e0c8277f2dcd.zip | |
Improve support for ExplainOneQuery() hook
There is a hook called ExplainOneQuery_hook that gives modules the
possibility to plug into this code path, but, like utility.c for utility
statement execution, there is no corresponding "standard" routine in
the case of EXPLAIN executed for one Query.
This commit adds a new standard_ExplainOneQuery() in explain.c, which is
able to run explain on a non-utility Query without calling its hook.
Per the feedback received from a couple of hackers, this change gives
the possibility to cut a few hundred lines of code in some of the
popular out-of-core modules as these maintained a copy of
ExplainOneQuery(), adding custom extra information at the beginning or
the end of the EXPLAIN output.
Author: Mats Kindahl
Reviewed-by: Aleksander Alekseev, Jelte Fennema-Nio, Andrei Lepikhov
Discussion: https://postgr.es/m/CA+14427V_B4EAoC_o-iYYucRdMSOTfpuH9k-QbexffY1HYJBiA@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeMemoize.c')
0 files changed, 0 insertions, 0 deletions