Supabase APIBreaking changehigh
Supabase ships breaking Postgres 15.19/17.11 updates on Sep 28, 2026
- Detected
- Sep 28, 2026
- Effective
- Sep 28, 2026(took effect 49 days ago)
- Confidence
- 97%
What changed
Supabase is rolling out PostgreSQL 15.19/17.11 minor releases that include four potentially breaking changes: ltree indexes may need reindexing, pgcrypto stops decrypting legacy-cipher (Blowfish/CAST5) PGP data by default, btree_gist indexes on float columns containing NaN need reindexing, and custom operators with non-built-in selectivity estimators now require superuser to recreate.
What to do
Run the provided detection queries for each affected area. Reindex affected ltree and btree_gist indexes using REINDEX INDEX CONCURRENTLY. Re-encrypt pgcrypto data using cipher-algo=aes256. Recreate custom operators without RESTRICT/JOIN clauses or switch to built-in estimators. Upgrade available in dashboard from 2026-09-28.
Affected
model: ltree indexesmodel: pgcrypto pgp_sym_encrypt/pgp_pub_encrypt (bf/blowfish/cast5 cipher)model: btree_gist indexes on float columnsmodel: custom operators with non-built-in selectivity estimatorsSource: supabase.com (Supabase's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Supabase SDK and the names above:
Or let Breakwatch do it: connect a repo and see which files call Supabase, then get the next change as an alert pointing at those files. Check a repo free