1
Feature request: Support pg_orca (Cascades-style query optimizer) as an alternative PostgreSQL optimizer
Source: supabase/supabase#49794 · opened by @yjhjstz
Feature request Is your feature request related to a problem? PostgreSQL's built-in planner occasionally produces suboptimal plans for complex analytical queries (multi-way joins, subqueries, CTEs). A new open-source extension, [pg_orca]( is a PostgreSQL port of the ORCA query optimizer — a Cascades-style, cost-based optimizer — and could offer significant performance improvements for such workloads. Describe the solution you'd like It would be great if Supabase could evaluate and support pg_orca as an optional optimizer for Postgres projects, e.g.: • Making the extension available via the Supabase dashboard (Database > Extensions) and in hosted Postgres images • Allowing users to enable/disable it per database or per session • Documentation on when it helps (analytical / join-heavy workloads) vs. when the default planner is fine Describe alternatives you've considered • Sticking with the stock PostgreSQL planner (status…
No pledges yet. Be the first to back this.
Comments
Similar requests
Configure External PostgreSQL for Supabase Instead of supabase-db
3 votes · 0 comments
pgx-managed Postgres w/ wrappers behaved differently from locally-installed Postgres w/ wrappers
2 votes · 0 comments
Add PL/PRQL extension
6 votes · 0 comments
Add secret-safe temporary PostgreSQL access for MCP-managed branches
1 vote · 0 comments
[Feature Request] Call other saved SQL queries from Dashboard query
1 vote · 0 comments
No comments yet.