pg_isready over internal network
Hi, I'm new to railway, so sorry if this q has an easy answer I somehow can't find.
I have a postgres db on railway and another process that is trying to call pg_dbisready --dbname=<DB_PRIVATE_URL>. The log says "postgres.railway.internal:5432 - no response". This makes me think something about my db config is wrong and it's rejecting connections over the internal network. It works with the standard (viaduct.proxy.rlwy.net) url, but I think this means I pay for data transfer?
11 Replies
Project ID:
5bcf11b0-2e3b-4e09-8ca6-5f10085d0b1c5bcf11b0-2e3b-4e09-8ca6-5f10085d0b1c
Project ID: 5bcf11b0-2e3b-4e09-8ca6-5f10085d0b1c
do you mean
pg_isready?yes, sorry, typo
are you building your app with nixpacks?
I've tried one with nixpacks and another simpler jsnode docker
jsnode to simply call pg_isready
at what point in your apps lifecycle are you running the command with either nixpacks or a dockerfile
shortly after startup. DB was deployed and active the whole time
Solution
try to add a 3 second sleep before starting your app/pg_isready
this works. thanks
no problem!
oh and
the standard (viaduct.proxy.rlwy.net) url, but I think this means I pay for data transfer?yes you would be subject to egrees fees when using the public tcp proxy, in contrast there is indeed no egress fees when using the private network to communicate with the database