diff options
| author | Amit Langote <amitlan@postgresql.org> | 2024-09-09 11:55:38 +0900 |
|---|---|---|
| committer | Amit Langote <amitlan@postgresql.org> | 2024-09-09 15:59:06 +0900 |
| commit | 77aebe9a8d3cccd4c54b43be87a38f2bae614c76 (patch) | |
| tree | 4f8c492c61f8457d9e9657b67c6bbb62e8694c7a /src/backend/utils/adt/jsonpath_exec.c | |
| parent | cd6b2ae3e7f64c881cb0159a2f9fc8d475e06d82 (diff) | |
| download | postgresql-77aebe9a8d3cccd4c54b43be87a38f2bae614c76.tar.gz postgresql-77aebe9a8d3cccd4c54b43be87a38f2bae614c76.zip | |
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.universality@gmail.com>
Author: Jian He <jian.universality@gmail.com>
Author: Amit Langote <amitlangote09@gmail.com>
Discussion: https://postgr.es/m/CACJufxEo4sUjKCYtda0_qt9tazqqKPmF1cqhW9KBOUeJFqQd2g@mail.gmail.com
Backpatch-through: 17
Diffstat (limited to 'src/backend/utils/adt/jsonpath_exec.c')
0 files changed, 0 insertions, 0 deletions