The Wire · Showcase
POSTGRES 17.6 LANDS WITH ORIOLEDB SUPPORT, CLI SHIPS CONFIG PUSH OVERHAUL
By RepoJournal · Filed · About Supabase
Supabase pushed five new Postgres distributions across 15.x and 17.x lines while CLI finally replaces its Go proxy for native config push across all five services.
The Postgres desk shipped 17.6.0.089 and 17.6.1.132 with OrileDB support [1] [2], paired with matching 15.14.1 patches [3] to keep older instances current. These distributions span multiple pgcron configurations [4] [5], giving operators granular control over job scheduling on their most critical workload versions. The CLI team delivered the month's most significant refactor: porting `supabase config push` from a Phase-0 Go proxy to native Effect in the legacy shell [10], eliminating a proxy layer and unifying config pushes across API, DB, auth, storage, and webhooks in a single `GET diff confirm PATCH` flow. Separately, `supabase db pull` now skips pg_dump entirely when using the pg-delta diff engine [11], fixing a silent ownership destruction bug that plagued large schema migrations. On the console side, the team shipped a dedicated Hosted Postgres landing page [6], removed three unexposed extensions from docs to reduce confusion [7], fixed token scope display after org deletion [8], and patched a critical logs UI bug where sidebar filters simply didn't work [9]. Supavisor hardened IPv6 hostname auto-detection [12] so operators can point at IPv6-only metadata databases without touching config knobs, achieving parity with tenant DB handling.
Action items
- → Deploy new Postgres 17.6.1.132 or 15.14.1 distributions to production instances for pgcron stability supabase/postgres [plan]
- → Upgrade CLI and run `supabase config push` to test the new native Effect implementation before relying on Go proxy removal supabase/cli [monitor]
- → Test logs sidebar filters in dashboard after the fix lands; previous UI clicks were silently failing supabase/supabase [immediate]
- → Update IPv6 metadata DB hostname in Supavisor config if running on IPv6-only infrastructure supabase/supavisor [plan]
References
- [1] 17.6.0.089-orioledb-pgcron-10-x86 ↗ supabase/postgres
- [2] 17.6.1.132-pgcron-10-x86 ↗ supabase/postgres
- [3] 15.14.1.132-pgcron-10-x86 ↗ supabase/postgres
- [4] 17.6.0.089-orioledb-pgcron-6-x86 ↗ supabase/postgres
- [5] 17.6.1.132-pgcron-6-x86 ↗ supabase/postgres
- [6] Added a Hosted Postgres page (#46674) supabase/supabase
- [7] docs: Remove unexposed extensions (#46686) supabase/supabase
- [8] fix: check token.scope for access resource display (#46603) supabase/supabase
- [9] fix(unified-logs): apply sidebar facet filters on click (#46589) supabase/supabase
- [10] feat(cli): port config push (#5489) supabase/cli
- [11] fix(cli): skip pg_dump in db pull when using pg-delta diff engine (#5255) supabase/cli
- [12] fix: auto-detect ipv6 from metadata db hostname (#1027) supabase/supavisor
FAQ
- What changed in Supabase on June 9, 2026?
- Supabase pushed five new Postgres distributions across 15.x and 17.x lines while CLI finally replaces its Go proxy for native config push across all five services.
- What should Supabase teams do about it?
- Deploy new Postgres 17.6.1.132 or 15.14.1 distributions to production instances for pgcron stability • Upgrade CLI and run `supabase config push` to test the new native Effect implementation before relying on Go proxy removal • Test logs sidebar filters in dashboard after the fix lands; previous UI clicks were silently failing
- Which Supabase repositories shipped on June 9, 2026?
- supabase/postgres, supabase/supabase, supabase/cli, supabase/supavisor