-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PG17 compatibility: Resolve compilation issues #7651
Closed
Closed
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
ae3ed7d
Enable configure
naisila 3f5a1e0
Rename foreach_ macros to foreach_declared_ macros
naisila a816d1b
Remove ExecFreeExprContext call
naisila 646ff0a
PG17 uses streaming IO in analyze, fix scan_analyze_next_block function
naisila 85a3ed0
Define ObjectClass for PG17+ only since it's removed
naisila 2434eff
No new node-wide object added so far in PG17, change assert
naisila 2076339
Remove ReorderBufferTupleBuf structure.
naisila e9fe257
Define colliculocale and daticulocale since they have been renamed
naisila e33736e
makeStringConst defined in PG17
naisila 4eafd3a
RangeVarCallbackOwnsTable was replaced by RangeVarCallbackMaintainsTable
naisila be2bec0
attstattarget is nullable, define pg compatible functions for it
naisila 0176974
stxstattarget is nullable in PG17, write compat functions for it
naisila dd19847
Use ResourceOwner to track WaitEventSet in PG17
naisila 022ca99
getIdentitySequence now uses Relation instead of relation_id
naisila e0a0874
Remove no-op tuplestore_donestoring function
naisila 49f7bff
MergeAction can have 3 merge kinds (now enum) in PG17, write compat
naisila a23bf88
EXPLAIN (MEMORY) is added, make changes to ExplainOnePlan
naisila 651bcc7
LIMIT_OPTION_DEFAULT has been removed as it's useless, use LIMIT_OPTI…
naisila ec9beb5
write compat for create_foreignscan_path bcs of more arguments in PG17
naisila 140a443
pgprocno and lxid have been combined into a struct in PGPROC
naisila 76f60a7
add pg17 build test
naisila File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you consider using the macros from pg17 (e.g. removing the local variables)? Would it be feasible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still have to support PG15 and PG16. One way to do it would be to change Citus's current definition of these macros such that they are identical to PG17's definitions, and then iterate over all uses and remove the local variables.
Do you think that is better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would require to add the macro definition for PG < 17. Both (the current / alternative) seem feasible options, and both require quite some editing. You already implemented one of them. It seems OK to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@naisila, personally I think that using PG17's definitions when
PG_VERSION_NUM >= PG_VERSION_17
and having identical definitions for PG15 and PG16 is better for you will naturally transition to PostgreSQL's macros when you no longer have to support PG15 and PG16. If you keep your own macros, you'll still have to support them even when PG15 and PG16 are no longer supported, or replace them with PostgreSQL's macros in the future.Anyway, that's just my opinion, I'm not the one who'll have to support Citus, so it's not my call.