Postgres on Railway now has:
48K followers
16,285 views
19 Comments
Comments from the original post on X (Twitter)

@simonhull
If I host it somewhere else you'll still try to access it too though right?
17 likes

@ConnorVG
Awesome, so you can break into our Postgres databases too! Thanks @Railway
10 likes

@georgiecanada
zero trust.
5 likes

@cow_in_sf
high availability except a couple times a month
4 likes

@JP__Gallegos
and a guy hacking u in real-time
4 likes

@NiggaGarryTan
lets start with removing this obvious lie on your status page
3 likes

@EliYumnik
Guys I really appreciate the built in connection pooling, thank you. Everyone has PR nightmares every now and then. Keep these updates going, happy customers like myself will be happy to stay with you.
1 like

@ryanlelek
a bit tone deaf
1 like

@GlanzJacob
High availability hahahaha

@Talljackcv
Can a point-in-time restore create a separate database so you can check the recovered data before switching the app over? Would love a short demo of that path.

@vibethecode
Agent skills on Postgres are powerful — so gate writes. Schema/migrate/drop need a human-approved write scope; reads can be freer. Auto CVE patching is great; agent YOLO on prod data isn't.

@illulachy_
curious what 'agent skills & cli support' covers for postgres. can an agent run a point-in-time restore through the cli, or is it limited to provisioning and queries?

@iwantnoproblems
the best

@luffyselah
Automatic failover on Postgres is a big upgrade for small teams.

@aimclubpro
man you suck

@MarkBrushkey
No thanks, wouldn’t want you to try to hack me outta nowhere just because it’s a slow day.

@mmhornbacher
PostGIS support and Branching yet?

@brachkow
Sadly, running Postgres that now lives on weak $6 VM cost me up to $45 in Railway compute, and the number kept creeping up

@iamayushrawat
Best update ever thank you team 🫶🏼
