7
Support for Custom PostgreSQL Extensions
Source: supabase/supabase#33754 · opened by @bin-bash-mak
Currently, Supabase supports a curated set of pre-approved PostgreSQL extensions, because it "helps ensure security and stability in the managed environment". However, this approach limits users who require custom database functionality implemented through PostgreSQL extensions. As discussed in issue [14325]( the only way to currently add an extension is via pg_tle, installing it from [database.dev]( or using one of the pre-approved ones. But the problem is that I have an extension built with [pgrx]( and I can't add it to my Supabase project. Now with the already available set of extensions / tools, I can already do what I want in plpgsql or in a node function. But I think it would be nice to add the ability to push extensions similar to how edge functions are pushed. I also am not sure but I would assume that the native part of the extension inherits the database process permission. But if there's a way to somehow sandbox them or restrict the access t…
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
Feature request: Support pg_orca (Cascades-style query optimizer) as an alternative PostgreSQL optimizer
1 vote · 0 comments
pgx-managed Postgres w/ wrappers behaved differently from locally-installed Postgres w/ wrappers
2 votes · 0 comments
Add secret-safe temporary PostgreSQL access for MCP-managed branches
1 vote · 0 comments
Add PL/PRQL extension
6 votes · 0 comments
No comments yet.