diff options
| author | Michael Paquier <michael@paquier.xyz> | 2022-10-24 16:53:54 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2022-10-24 16:53:54 +0900 |
| commit | 2e0d80c5bb722fb49a4cdc44b0c715ec77c83f79 (patch) | |
| tree | eec397d42d6302a978229dccce5f1dfd8482dfde /src/backend/parser/parse_clause.c | |
| parent | 3cf2f7af7f9b6198f3d518aaffb0ff4de340c5bc (diff) | |
| download | postgresql-2e0d80c5bb722fb49a4cdc44b0c715ec77c83f79.tar.gz postgresql-2e0d80c5bb722fb49a4cdc44b0c715ec77c83f79.zip | |
Improve coverage of ruleutils.c for SQLValueFunctions
While looking at how these are handled in the parser and the executor, I
have noticed that there is no test coverage for most of these when
reverse-engineering an expression for a SQLValueFunction node in
ruleutils.c, including how these are reparsed when included in a FROM
clause. Some hacking in this area has showed me that these could break
easily, so add some coverage to track the existing compatibility.
Extracted from a much larger patch by me.
Discussion: https://postgr.es/m/YzaG3MoryCguUOym@paquier.xyz
Diffstat (limited to 'src/backend/parser/parse_clause.c')
0 files changed, 0 insertions, 0 deletions