Reduce queries to detect select privileges for PostgreSQL relations #57389
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
Use a single query rather than 3 to determine recovery status, select privilege and update/insert/delete privileges. Also drops the need to evaluate view definitions to determine selectability.
jef-n
approved these changes
May 10, 2024
|
Now creation/clone of a prostgres layer based on a large view takes 0.10 seconds rather than 20 seconds (it was depending on the size of the view). Also projects are loading faster. |
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.
Use a single query rather than 3 to determine recovery status, select privilege and update/insert/delete privileges.
Also drops the need to evaluate view definitions to determine selectability.
User in chat reported 20 seconds of time for such evaluation.