critical90%
PG 15→17 upgrade fails at completion due to missing pg_cron update path, leaving project in unrecoverable state
An in-place Postgres 15 to 17 upgrade on Supabase aborts during the completion step because the extension pg_cron has no update path from version 1.6 to 1.6.4. This leaves the database running on PostgreSQL 17.6.1.127 but with rest/auth services down, no valid restart target, and no self-service recovery path.