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.
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
Expose
default_transaction_...
Postgres settings #8276Expose
default_transaction_...
Postgres settings #8276Changes from 8 commits
bd5d23d
6697be9
1706493
e7832b0
e31586a
85f807a
956e89c
bda5cb3
003e569
95f5ef7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do you think we should try to invalidate the persistent cache because of this change, or should we just instruct affected users to clear the cache manually?
(This is a more general question about miscompilation bugs and the persistent cache that I'm not sure we've ever properly figured out)
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.
Oh true! One way that might work is to always "upgrade" the persistent cache automatically after server upgrade (by recompiling the cached queries) even if there are no compiler changes - if it's already in downtime maintenance, why not make the most of it and make sure the query cache is up to date. Let me draft a PR for that.
I'd use that as the last resort when we failed to make the server fix itself (which is likely the case now, but let me fix that).
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.
Is extending the downtime (possibly by a lot) better than a cache flush? It's not totally obvious to me.
Maybe it would be best to come up with an empty cache and then repopulate in the background?
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.
I don't consider cache recompilation to be a release blocker, by the way; it's been an outstanding issue through all of 5.0, so we can live with it a little longer.
(Fixing it is still good, though; but lower priority than getting this PR finalized and landed)