ops: create the _supabase database Supavisor needs - #301
Merged
Merged
Conversation
The pooler was crashlooping on FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist and had reached 439 restarts. Nothing else depends on the pooler, so it hid completely: every other container reported healthy and the site served fine the entire time. It only surfaced because a container count came back 12 healthy / 1 not, and 'Up 2 seconds' turned out to mean a restart loop rather than a slow start. Same root cause as the auth/storage/graphql_public/_realtime repairs: the very first initdb ran with a config postgres could not read, so the image's bootstrap never created it, and every start since logged 'Skipping initialization'. Now repaired idempotently alongside the others - five, not four. Fixed on dev2: pooler healthy, 0 restarts, 13/13 containers healthy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan48 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 31 | LOW: 15
Snippets are redacted; ThreatCrush never prints matched credential material. |
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
1 participant
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.
The pooler was crashlooping on
and had reached 439 restarts.
It hid completely. Nothing else depends on the pooler, so every other container reported healthy and the site served fine throughout. It only surfaced because a container count came back 12 healthy / 1 not — and
Up 2 secondsturned out to mean a restart loop rather than a slow start.Same root cause as the auth / storage / graphql_public / _realtime repairs already in
setup-supabase.sh: the very first initdb ran with a config postgres could not read, so the image's bootstrap never created it, and every start since loggedSkipping initialization. That makes five of these, not four.Fixed on dev2 — pooler healthy at 0 restarts, 13/13 containers healthy, verified stable over 75s rather than caught mid-cycle. Creates only the new database and its two schemas; the nichedb database sharing this cluster is untouched.