From b57a412ac4c3093cb5dbcc7a64ea494aedb6afe0 Mon Sep 17 00:00:00 2001 From: Oliver Rice Date: Fri, 7 Mar 2025 08:56:18 -0600 Subject: [PATCH] pgmq don't manipulate sequences 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 --- .../pg_upgrade_scripts/complete.sh | 67 ------------------- 1 file changed, 67 deletions(-) diff --git a/ansible/files/admin_api_scripts/pg_upgrade_scripts/complete.sh b/ansible/files/admin_api_scripts/pg_upgrade_scripts/complete.sh index 515c490f6..a638915f0 100755 --- a/ansible/files/admin_api_scripts/pg_upgrade_scripts/complete.sh +++ b/ansible/files/admin_api_scripts/pg_upgrade_scripts/complete.sh @@ -82,73 +82,6 @@ EOF # Patching pgmq ownership as it resets during upgrade HAS_PGMQ=$(run_sql -A -t -c "select count(*) > 0 from pg_extension where extname = 'pgmq';") if [ "$HAS_PGMQ" = "t" ]; then - PATCH_PGMQ_QUERY=$(cat <