SQL/JSON: Avoid initializing unnecessary ON ERROR / ON EMPTY steps When the ON ERROR / ON EMPTY behavior is to return NULL, returning NULL directly from ExecEvalJsonExprPath() suffices. Therefore, there's no need to create separate steps to check the error/empty flag or those to evaluate the the constant NULL expression. This speeds up common cases because the default ON ERROR / ON EMPTY behavior for JSON_QUERY() and JSON_VALUE() is to return NULL. However, these steps are necessary if the RETURNING type is a domain, as constraints on the domain may need to be checked.
Reported-by: Jian He <jian.universal...@gmail.com> Author: Jian He <jian.universal...@gmail.com> Author: Amit Langote <amitlangot...@gmail.com> Discussion: https://postgr.es/m/cacjufxeo4sujkcytda0_qt9tazqqkpmf1cqhw9kbouejfqq...@mail.gmail.com Backpatch-through: 17 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/77aebe9a8d3cccd4c54b43be87a38f2bae614c76 Modified Files -------------- src/backend/executor/execExpr.c | 32 ++++++++++++++++++++++++++------ src/backend/executor/execExprInterp.c | 14 ++++++++------ 2 files changed, 34 insertions(+), 12 deletions(-)
