Filter out extension-related operations in creation scripts of history table #3713
+46
−1
Conversation
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
…to prevent superuser permission errors and add related test.
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.
Some Managed PostgreSQL services (e.g., Azure Flexible Server) do not grant users permission to create extensions, just superusers. Previously, when extensions like NetTopologySuite were configured, efcore.pg would include
CREATE EXTENSION IF NOT EXISTS postgis;in every GetCreateScript() initialization script on startup, which then would break the application because of this permission error.This PR adds a workaround to filter out extension-related operations from the creation scripts of the history table.
Fixes #3496