Skip to content

feat: handle pg_net persistence mismatch for PG14 upgrade#2230

Open
cfunkhouser wants to merge 2 commits into
developfrom
cfunk/indata-757-handle-pg_net-persistence-mismatch-before-pg14-auto-upgrades
Open

feat: handle pg_net persistence mismatch for PG14 upgrade#2230
cfunkhouser wants to merge 2 commits into
developfrom
cfunk/indata-757-handle-pg_net-persistence-mismatch-before-pg14-auto-upgrades

Conversation

@cfunkhouser

Copy link
Copy Markdown

Execute ALTER TABLE net.http_request_queue SET LOGGED on PG14 databases before upgrade.

There is a state mismatch in which net.http_request_queue_id_seq sequence is logged, but the table net.http_request_queue is not. This mismatch prevents pg_upgrade from proceeding. This change forces that alteration to occur at upgrade initiation time, before any of the other upgrade process has occurred.

@cfunkhouser cfunkhouser requested review from a team as code owners June 18, 2026 23:52

@Crispy1975 Crispy1975 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants