feat(expr): implement pg_get_keywords()
and pg_keywords
#17033
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Runji Wang [email protected]I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
resolve #17023
This PR implements
pg_get_keywords()
function andpg_keywords
system catalog.However, the implementation is not entirely correct. There are many rows in the output that have a different category than postgres. I don't fully understand how to map our reserved keyword tables to the category defined by PG. But if it's just to resolve the problem mentioned in #17023, maybe non-empty output is enough.
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
Support
pg_get_keywords()
function andpg_keywords
system catalog.