Support for Custom PostgreSQL Extensions #33754
Replies: 16 comments 4 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.
-
|
Hi, |
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.
-
|
I'd like to suggest Periods, as explained at postgres wiki is the most complete implementation of temporal databases on postgres. (Also the only reason my company has not yet transitioned to Supabase) List of Extensions and Temporal Enhancements
|
Beta Was this translation helpful? Give feedback.
-
|
It seems that the More info can be found here: |
Beta Was this translation helpful? Give feedback.
-
|
This seems like an unmonitored thread but fwiw I would like to use https://github.com/turbot/steampipe-postgres-fdw with Supabase. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to ask for https://github.com/vibhorkum/pg_background It allows:
|
Beta Was this translation helpful? Give feedback.
-
|
I would like to suggest https://github.com/apache/age as a graph database extension it brings enormous value for not only AI applications in a graphrag sense. |
Beta Was this translation helpful? Give feedback.
-
|
PostgreSQL Anonymizer - https://postgresql-anonymizer.readthedocs.io/en/stable/ Or anything that could selectively mask PII in the process of creating a dump? The desire is to safely replicate prod data to the local dev environment. |
Beta Was this translation helpful? Give feedback.
-
|
PG_TEXTSEARCH - https://github.com/timescale/pg_textsearch BM25 in Postgres. See https://www.tigerdata.com/blog/you-dont-need-elasticsearch-bm25-is-now-in-postgres |
Beta Was this translation helpful? Give feedback.
-
|
I would like to suggest the pg_partman extension, essential for anyone who needs to work with partitioning. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
PostGIS - H3 please! Great companion to PostGIS for working with global hierarchical hex grid system. |
Beta Was this translation helpful? Give feedback.
-
|
Can we have https://github.com/bigsmoke/pg_mockable in local deployments? It'd be very useful to mock |
Beta Was this translation helpful? Give feedback.
-
|
pg_ivm please! |
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