Supabase APIBreaking changehigh
Supabase ships breaking Postgres 15.19/17.11 updates on Sep 28, 2026
- Detected
- Oct 5, 2026
- Effective
- Sep 28, 2026(took effect 49 days ago)
- Confidence
- 95%
What changed
PostgreSQL 15.19/17.11 minor release is being rolled out, requiring potential action for users of ltree indexes, pgcrypto legacy ciphers (bf/blowfish/cast5), btree_gist indexes on float columns with NaN, and custom operators with non-built-in selectivity estimators. Additionally, the Supabase Management API logs.all analytics endpoint is removed on 2026-09-23, requiring migration to the new ClickHouse-backed logs endpoint.
What to do
Run the provided detection queries for ltree, pgcrypto, btree_gist, and custom operator issues; reindex affected indexes using REINDEX INDEX CONCURRENTLY; re-encrypt pgcrypto data using AES; migrate any scripts calling logs.all to the new logs endpoint using ClickHouse SQL.
Affected
endpoint: logs.allendpoint: logsmodel: ltreemodel: pgcryptomodel: btree_gistmodel: pg_operatorSource: 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