3 months ago
https://github.com/railwayapp-templates/postgres-ssl/issues/17
Our Postgres templates currently do not support Postgres extensions.
We use the base debian-flavored official Postgres images, and each extension has an extra install step for the package and and init step for to bootstrap the extension on the Postgres instance. Typically, it's:
apt-get install postgresql-${MAJ_VERSION}-pgvector
psql -c 'CREATE EXTENSION IF NOT EXISTS vector;'If we want to bake an extension in, we'll need to ensure we install the extension on the image first.
We also don't want to bake all requested extensions in, so ideally we have a way for users to specify what extensions they want from a list of officially supported ones, and a sane way to do that (ex: RAILWAY_PG_EXTENSIONS variable).
If you'd like to see an extension, please leave a comment here!
1 Thread mentions this feature
7 Replies
3 months ago
I have same problem. Currently I don't know how to add extensions so I can't use Postgres from railway
3 months ago
Yes, postgis!
2 months ago
pg_vector please - there's a container in marketplace with pg_vector installed, but it doesn't support SSL
2 months ago
idk why we dont have this already, sure I can learn build it myself but surely there must be a easier way for (less experience) guy
18 days ago
this would be great because now one have to switch to a new image when decide to add a new extension. also custom postgres image does not have the table preview and other admin functionality...