builtins: add range, multirange types#165
Merged
bendrucker merged 2 commits intomasterfrom Jul 30, 2025
Merged
Conversation
bendrucker
force-pushed
the
builtins-range-types
branch
from
672eeb1 to
d7df75f
Compare
bendrucker
force-pushed
the
builtins-range-types
branch
from
d7df75f to
498534a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds OIDs for range and multirange types. Multiranges were added in PostgreSQL v14, so we need to use that to generate the OIDs. v11 supports regular range types, but not multi.
The generator confirms we now have a bunch of new types in v14 (including non-range ones like
JSONPATH), but a handful where we still need v11 to avoid a breaking change. v17 doesn't have any type changes compared to v14.Closes #161
Stacks on #164