Fix build errors with PostgreSQL v17 #501
Closed
Conversation
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
jcflack
added a commit
that referenced
this pull request
Oct 3, 2024
Credit to Francisco Miguel Biete Banon in PR #501. Simplified so the code now simply uses the new names (introduced in postgres/postgres@393b559), and defines them in older PG versions for compatibility.
jcflack
added a commit
that referenced
this pull request
Oct 3, 2024
SPI_restore_connection was defined as a noop since PostgreSQL 10, and the compatibility macro has been removed in postgres/postgres@75680c3. Because PL/Java 1.6 purports to still run on PostgreSQL 9.5, continue to use the function in PG < 10. Credit to Francisco Miguel Biete Banon in PR #501.
Merged
|
Closing in favor of PR #502. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Symbols renamed in PostgreSQL v17
SPI_restore_connection was defined as a noop since PostgreSQL 10, and the compatibility macro has been removed.
Commit removing compatibility macro
Closes #499