Supabase
Support for Custom PostgreSQL Extensions #33754
Replies: 4 comments 2 replies
-
|
Yeah that would be great! I think something could be done using web assembly. I see supabase has used web assembly with their wrappers - https://supabase.com/blog/postgres-foreign-data-wrappers-with-wasm |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. I did look at some examples in the repo https://github.com/supabase/wrappers but still doesn't look like a full extension alternative. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
My bad, I added a comment here: https://github.com/orgs/supabase/discussions/679#discussioncomment-14363676 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I'd like to suggest adding the pg_rrule extension (https://github.com/petropavel13/pg_rrule) to simplify date expansion for recurring events. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to suggest https://github.com/mpartel/postgres-protobuf for handling protobuf messages |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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 to specific parts of the underlying OS. could it help with the mitigation of the security concerns?
Beta Was this translation helpful? Give feedback.
All reactions