WhatBrokeToday
Today's Trends
minorResolvedSupabasevPG15 -> PG17

Supabase: PG15 -> PG17 Upgrade Failures

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(current)

Executive summary

A PG15 to PG17 upgrade in Supabase failed, affecting users who upgraded their database version. The issue has been resolved.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    PG15 -> PG17 Upgrade Failures(opens official status page in a new tab)

    Status: Resolved This issue is now resolved.

    by supabase status

Timeline

  1. First report on status page

    PG15 -> PG17 Upgrade Failures

    Source
  2. Official statement

    Status: Resolved This issue is now resolved.

    Source
  3. Status changed

    Status changed: new → resolved (official status page reports resolution).