AI & Agent Dev Bug Sandbox Back to Radar

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.

criticalConfidence 90%PostgreSQL Affected Vpg_cron 1.6 Affected VPostgreSQL 15 To 17 Upgrade

Origin Analysis

The upgrade completion process executes ALTER EXTENSION pg_cron UPDATE (or similar) which requires an update path from the installed version (1.6) to the target version (1.6.4). PostgreSQL's extension mechanism relies on version-specific update scripts (e.g., pg_cron--1.6--1.6.1.sql, etc.), and if no chain of scripts exists from the current version to the target, the command fails with 'extension "pg_cron" has no update path from version "1.6" to "1.6.4"'. The Supabase upgrade preflight did not verify the availability of update paths before starting the data migration, causing the completion phase to abort, skip finalization steps (such as collation refresh and reindexing), and leave the control plane without a valid restart target.

1. Have a Supabase project on PostgreSQL 15 with pg_cron extension version 1.6 installed (with scheduled jobs). 2. Trigger an in-place PostgreSQL 17 upgrade from the dashboard. 3. Data upgrade completes, but finalization fails with 'extension "pg_cron" has no update path from version "1.6" to "1.6.4"'. 4. Upgrade status becomes 5_data_upgrade_completion_failed; rest/auth become unhealthy, API requests return 503. 5. Dashboard 'Restart project' fails with 'Unable to locate a single valid target for the restart; found 0'.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This script is destructive: DROP EXTENSION ... CASCADE removes the cron schema and all dependent objects. The backup and restore of cron.job relies on identical table structures between the old and new versions; any schema changes may cause the INSERT to fail or lose data. Run this only during a maintenance window after taking a full physical backup. Ensure no active connections are using pg_cron during the operation. After executing, the platform control plane must still be repaired (e.g., reattach compute target, restart services) — this script does not fix the missing restart target. Rollback: if the script fails, restore from the most recent backup or use the backup table to reinstall the previous pg_cron version (if available). Test thoroughly in a staging environment first.