Self hosted Supabase - using TSL license instead of apache

TimescaleDB and PostgreSQL Installation, Configuration, and Errors
1

I’ve been hosting supabase for a while in railway. Our timeseries data has grown to a point where we need timescale to help scale. But after migrating my table to a hypertable I’m realizing that only the apache version is enabled in my docker contianer.

How can I update my setup to use the TSL version? Has anyone done this before and have any tips?

My thought was just updating or extending the current docker image (supabase/postgres) - but it seems like that might be more complex. Or should I switch out the supbase/postgres image with the timescaledb image? - I’m worried I’ll be missing out on things from the supabase image and have configuration differences.

2

Hi Nick, I’m not familiar with how Supabase image works, but you can certainly switch to the docker image that we offer.

You can also think about building your custom image for it.

As an alternative, you can also set FDW between two instances: