AI & Agent Dev Bug Sandbox Back to Radar

Repeated FATAL Errors Logging 'Database "Supabase_admin" Does Not Exist' On Hosted Supabase Projects

Starting June 29, 2026, multiple Free and Pro tier Supabase projects experienced rapid, recurring FATAL log entries indicating connection attempts to a non-existent 'supabase_admin' database. The errors originate from internal platform management processes, not user code, and clutter database logs without causing user-visible application failures.

mediumConfidence 75%Supabase

Origin Analysis

A Supabase internal management service is configured to connect to the database name 'supabase_admin', but that database does not exist in the affected project instances; the connection string or database parameter in the service's configuration is incorrect.

1. Log in to the Supabase Dashboard. 2. Navigate to Project Settings → Logs → Database Logs. 3. Observe recurring FATAL errors stating: database "supabase_admin" does not exist.

Fixing Code Block

// Example fix for the internal service configuration
// Replace erroneous database name with the actual admin/maintenance database (usually 'postgres')
// TypeScript/Node.js using pg Client

import { Client } from 'pg';

const client = new Client({
  host: process.env.PGHOST,
  port: Number(process.env.PGPORT),
  user: process.env.PGUSER,
  password: process.env.PGPASSWORD,
  // Fix: change database from 'supabase_admin' to the correct one
  database: 'postgres',
  ssl: { rejectUnauthorized: false }
});

client.connect()
  .then(() => console.log('Connected to management database'))
  .catch(err => console.error('Connection error', err.message));

The fix corrects the database name in the internal service's connection configuration from 'supabase_admin' to the actual database name (commonly 'postgres' or a dedicated management database). This eliminates the FATAL errors by ensuring the service connects to an existing database.

Edge Case Audit

Changing the database name may affect other internal components that expect the old name; verify that the service's required schemas and permissions exist in the target database. Rollback: revert the database parameter to the previous value and redeploy the service. Test in staging before production, and monitor connection success rates to ensure no new failures.