← Back to Supabase History
minor✓ Resolved

Issues propagating Postgres configuration updates

Supabase•Tue, Mar 17, 2026, 04:50 AM
Status
resolved
Duration
2h 54m
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedTue, Mar 17, 2026, 07:45 AM
This incident has been resolved.
monitoringTue, Mar 17, 2026, 07:07 AM
A fix has been implemented and we are monitoring.
identifiedTue, Mar 17, 2026, 05:11 AM
We have identified the root cause and are currently working on a fix.
investigatingTue, Mar 17, 2026, 04:50 AM
Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.

📊 TECHNICAL DETAILS

Internal ID
9d207110-5c12-4bee-aadf-477382e75b36
External ID
gg1sbqs5pr5l
🕐 Started
Tue, Mar 17, 2026, 04:50 AM
🔄 Last Updated
Tue, Mar 17, 2026, 07:45 AM
✓ Resolved
Tue, Mar 17, 2026, 07:45 AM
MINOR
Impact Level
2h 54m
Total Duration
3
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed