[Backport release-3_10] [postgres] Fix superslow layer instantiation in huge databases by only fetching type info of used fields. #38180
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
…y fetching type info of used fields.
|
@borysiasty could we skip the 3.10 backport for this one? I'd say it's a high-risk change, and given this issue has been around since...forever(?)... I think the risk of regressions outweighs the reward of the backport. |
|
@nyalldawson of course, sorry for not objecting earlier :) You added the backport label, so I waited to see if there is more supporters. |
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.
Backport a29b3aa from #38158