Management API Postgres config updates overwriting previous updates

Summary

Management API Postgres config updates overwriting previous updates

Connection Logging feature is working fine for all customers now.

• Started

  Nov 3, 2026 · 4:56 AM

• Resolved

  Nov 3, 2026 · 7:04 AM

• Duration

  2h 8m

• Severity

  None

• ◐

  Investigating

  Nov 3 · 4:56 AM Supabase

  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)

• ◐

  Investigating

  Nov 3 · 5:16 AM Supabase

  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.

• ◉

  Monitoring

  Nov 3 · 6:17 AM Supabase

  We have identified the cause and are deploying a fix. The dashboard setting that was temporarily disabled will soon be enabled again.

• ◉

  Monitoring

  Nov 3 · 6:24 AM Supabase

  A fix has been deployed, and the Connection Logging setting that was temporarily disabled on the dashboard is available again.

• ✓

  Resolved

  Nov 3 · 7:04 AM Supabase

  Connection Logging feature is working fine for all customers now.