Skip to content

pgmq don't manipulate sequences during upgrade #1471

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

Merged
merged 2 commits into from
Jul 7, 2025

Conversation

olirice
Copy link
Contributor

@olirice olirice commented Mar 7, 2025

The script being deleted was a hacky solution we put in place to resolve a pg_dump segfault due to its interaction with pgmq tables. It currently introduces errors where sequences become owned by supabase_admin and are inaccessible to users after upgrading. https://supabase.slack.com/archives/C05Q0CVC65B/p1741093731995359

This update mirrors the same code's removal from our on-backup hook here: https://github.com/supabase/infrastructure/pull/21405/files

The script being deleted was a hacky solution we put in place to resolve a pg_dump segfault due to its interaction with pgmq tables. It currently introduces errors where sequences become owned by supabase_admin and are inaccessible to users after upgrading.
https://supabase.slack.com/archives/C05Q0CVC65B/p1741093731995359


This update mirrors the same code's removal from our on-backup hook here: https://github.com/supabase/infrastructure/pull/21405/files
@olirice olirice requested a review from a team as a code owner March 7, 2025 14:56
@olirice olirice changed the title pgmq don't manipulate sequences pgmq don't manipulate sequences during upgrade Mar 7, 2025
@pcnc
Copy link
Member

pcnc commented Mar 7, 2025

@samrose
Copy link
Collaborator

samrose commented Mar 25, 2025

@olirice @pcnc how can I help move this forward?

@olirice
Copy link
Contributor Author

olirice commented Mar 25, 2025

@pcnc would be good to get this one reviewed as pg17 will likely trigger a lot of upgrades

@samrose
Copy link
Collaborator

samrose commented Mar 25, 2025

Maybe needs rebase and testing?

@soedirgo soedirgo requested a review from a team as a code owner July 7, 2025 18:21
Copy link
Collaborator

@samrose samrose left a comment

Choose a reason for hiding this comment

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

@soedirgo just need to update vars.yml versions to get this released

@soedirgo
Copy link
Member

soedirgo commented Jul 7, 2025

Shouldn't need to do that, we just need to trigger the publish pg_upgrade scripts job

@soedirgo
Copy link
Member

soedirgo commented Jul 7, 2025

Tested on local infra, fixed sequence ownership issues for both 15 -> 17 and 17 -> 17

@soedirgo soedirgo merged commit 48f22dd into develop Jul 7, 2025
19 checks passed
@soedirgo soedirgo deleted the or/pgmq-upgrade-seqs branch July 7, 2025 19:22
samrose added a commit that referenced this pull request Jul 7, 2025
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.

4 participants