Replies: 15 comments 31 replies
-
| 
         You might consider marking these somehow in the current dashboards as deprecated or similar to reduce new use of them.  | 
  
Beta Was this translation helpful? Give feedback.
-
        
  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Is there an easy way to see where/why extensions were installed? I'm trying to figure out why I have   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Thanks for removing timescaledb, they didn't deserve to been in an open-source project with their bad license.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         I tried to spin locally   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         One thing that would really help is if the CLI had an "upgrade" option similar to the dashboard. I know I can edit the Postgres-version file, but that doesn't update the versions of the other images. The only way right now to see what those versions are is to do an upgrade in the cloud and then link locally. I can then test in the safety of my local environment, which by definition is allowed to break and be wiped.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Any ETA for the v17 drop?  | 
  
Beta Was this translation helpful? Give feedback.
-
        
 Will there be a replacement for the hyperfunctions?  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         I am actively using   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         What is the reasoning for dropping support for plv8? And edge functions aren't an option since both of these use cases must be run idempotently and atomically.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         I am also not too happy about dropping   | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Supabase has been shiling plv8 for a while, dropping this now is extremely disappointing... we use it to share RBAC logic between RLS and backend. Migrating this will be an insane headache. Might even warrant migrating away from Supabase altogether.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Hi @samrose ,  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Upgraded this morning. Total breeze, no issues. Took 6mins 👍  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Is pg_partman still expected at the end of october?  | 
  
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The upcoming release of Supabase Platform will use Postgres 17. The Postgres 17 bundle will no longer include the following Postgres extensions:
timescaledbplv8pllsplcoffeepgjwtExisting projects will NOT be immediately impacted - the extensions will continue to be supported on Supabase Postgres 15, until the Supabase Platform “end of life” of Postgres 15 in approximately 1 year (May 2026). However, the extensions will not receive further updates and fixes. Existing projects will need to drop the extensions before they can upgrade to Postgres 17.
This decision to deprecate these extensions was not made lightly, however these extensions are more complex than “standard” Postgres extensions and require additional support/testing that did not match the usage we see on the platform.
To address the capability gaps left by deprecating plv8 and timescaledb, we plan to include the pg_partman extension in a future Postgres 17 release and will provide documentation to help migrate Timescale hypertables to native Postgres partitioning at that time. For plv8 we recommend porting the logic to Edge Functions, which offer greater scalability and flexibility. These changes are part of our ongoing efforts to streamline our platform, reduce operational complexity, and ensure long-term support for features that align closely with our user base.
If you have additional use-cases for these deprecated extensions, please reach out to us and our Success team will work with you to find a solution.
Beta Was this translation helpful? Give feedback.
All reactions