Local Supabase: Analytics/Logflare Schema Not Created, No Logs in Studio

[whitfa99]

Description:

When running Supabase locally (latest CLI, Docker, and config), the _analytics schema and log tables are not created. As a result, the Studio logs UI shows no logs for any service, and the Logflare container logs errors about missing tables/columns. This persists after full reinit/reset, and is not caused by any custom migrations.

Steps to Reproduce:

1. npx supabase init
2. npx supabase start
3. Perform actions (e.g., upload files, create tasks)
4. Visit Studio logs page — no logs appear
5. Inspect DB: _analytics schema/tables are missing
6. Logflare container logs show errors about missing columns/tables

Expected Behavior:

The _analytics schema and log tables should be created automatically, and logs should appear in Studio.

Actual Behavior:

No analytics schema/tables, no logs in Studio, Logflare errors in container logs.

Environment:

• OS: Manjaro Linux
• Supabase CLI: 2.31.8 (latest)
• Docker Compose: (installed, latest)
• Supabase config: [analytics] enabled = true, [realtime] enabled = false, etc.
• No custom migrations touch analytics/logging schemas

Relevant Logs:

• Logflare container:

column "body" does not exist
operator does not exist: jsonb ~~ unknown

What I’ve Tried:

• Full reinit/reset (npx supabase db reset --local)
• Reinstalling CLI and Docker images
• Ensured no custom migrations touch analytics/logging
• Searched GitHub issues and docs

[twhittock]

Reverting back to 2.29.0 from 2.31.8 fixed the logs for me, after deleting the db.network_restrictions config section.