feat: handle pg_net persistence mismatch for PG14 upgrade#2230
Open
cfunkhouser wants to merge 2 commits into
Open
feat: handle pg_net persistence mismatch for PG14 upgrade#2230cfunkhouser wants to merge 2 commits into
cfunkhouser wants to merge 2 commits into
Conversation
Crispy1975
approved these changes
Jun 19, 2026
Crispy1975
left a comment
Contributor
There was a problem hiding this comment.
LGTM; we have a ConfigCat allowPg14LaunchOrgs flag which allows an org slug to be added. This mean we can spin up a PG14 project and then do surgery to mimic the conditions we're gonna fix.
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
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.
Execute
ALTER TABLE net.http_request_queue SET LOGGEDon PG14 databases before upgrade.There is a state mismatch in which
net.http_request_queue_id_seqsequence is logged, but the tablenet.http_request_queueis not. This mismatch preventspg_upgradefrom proceeding. This change forces that alteration to occur at upgrade initiation time, before any of the other upgrade process has occurred.