Skip to content

docs: update postgis relocation runbook with verified prod state#113

Merged
erichare merged 1 commit into
mainfrom
docs/postgis-relocation-prod-verified
Jun 10, 2026
Merged

docs: update postgis relocation runbook with verified prod state#113
erichare merged 1 commit into
mainfrom
docs/postgis-relocation-prod-verified

Conversation

@erichare

Copy link
Copy Markdown
Owner

Records the live-verified state of project qijajhckwxsclvyzeaez (PostGIS 3.3.7 in public, postgres not superuser, spatial_ref_sys grants all from supabase_admin → self-service relocation and REVOKE both confirmed impossible), corrects the support-ticket SQL to UPDATE TO "3.3.7next" per Supabase's troubleshooting docs ("ANY" only exists on PostGIS ≥ 3.5), and notes that relocation also clears the six st_estimatedextent SECURITY DEFINER advisor warnings (0028/0029). Docs-only change.

Live state of qijajhckwxsclvyzeaez checked via the Supabase MCP: PostGIS
3.3.7 in public owned by supabase_admin, postgres not superuser, and all
anon/authenticated grants on spatial_ref_sys have grantor supabase_admin —
confirming both self-service paths (in-place relocation, REVOKE) are dead
ends and the support ticket is the only non-destructive option.

Corrects the ticket SQL to the version Supabase's troubleshooting section
prescribes for 3.3.7 (UPDATE TO "3.3.7next"; "ANY" only exists on >= 3.5,
which is what our CI validation used). Also records that relocation clears
six additional advisor WARNs (0028/0029 on public.st_estimatedextent, a
SECURITY DEFINER postgis function exposed at /rest/v1/rpc) beyond 0013/0014.
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
aeroza-web Ready Ready Preview, Comment Jun 10, 2026 5:01pm

Request Review

@erichare erichare merged commit a67ba7a into main Jun 10, 2026
11 of 12 checks passed
@erichare erichare deleted the docs/postgis-relocation-prod-verified branch June 10, 2026 17:07
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.

1 participant