Management API Postgres config updates overwriting previous updates
Nov 3, 04:56 UTCNov 3, 07:04 UTC
Duration
2h 8m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
53 incidents
Affected
Not listed by the vendor.
Final update
Connection Logging feature is working fine for all customers now.
Timeline
- Resolved · Nov 3, 07:04 UTC
Connection Logging feature is working fine for all customers now.
- Monitoring · Nov 3, 06:24 UTC
A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.
- Monitoring · Nov 3, 06:17 UTC
We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.
- Investigating · Nov 3, 05:16 UTC
We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent. Past changes are being overwritten For now, we have disabled making certain Postgres config changes on the dashboard until the issue is resolved.
- Investigating · Nov 3, 04:56 UTC
We are actively correcting an issue with the Management API: • Postgres Config changes only save the latest values sent, past changes are not being saved For now please refrain from not making any Postgres Config changes via the [Management API](https://supabase.com/docs/reference/api/introduction) or in the [Database Settings Dashboard](https://supabase.com/dashboard/project/\_/database/settings)