You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] latest
[ ] @next
[x ] 0.2.20 (or put your version here)
Hello,
I'm seeing the problem that at one point in a Google Cloud function environment Typeorm looses the database connection to Postgres "Connection terminated unexpectedly".
That by itselfs is probably not that big of an issue because as I understand it Typeorm automatically reconnects when the connection has been lost. (I confirmed this in local tests where I simply shut down the database server, watching the application recovering on its own)
My problem is that this does not happen in our production environment.
After seeing the "Connection terminated unexpectedly" error the connection continues to fail with the error "Client has encountered a connection error and is not queryable".
Can you point me to some approach to handling this failing connection?
How can I detect this condition and how can I reconnect?
Maybe there's some configuration that is missing?
The text was updated successfully, but these errors were encountered:
Issue type:
[x ] question
[ ] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ]
cordova
[ ]
mongodb
[ ]
mssql
[ ]
mysql
/mariadb
[ ]
oracle
[x ]
postgres
[ ]
cockroachdb
[ ]
sqlite
[ ]
sqljs
[ ]
react-native
[ ]
expo
TypeORM version:
[ ]
latest
[ ]
@next
[x ]
0.2.20
(or put your version here)Hello,
I'm seeing the problem that at one point in a Google Cloud function environment Typeorm looses the database connection to Postgres "Connection terminated unexpectedly".
That by itselfs is probably not that big of an issue because as I understand it Typeorm automatically reconnects when the connection has been lost. (I confirmed this in local tests where I simply shut down the database server, watching the application recovering on its own)
My problem is that this does not happen in our production environment.
After seeing the "Connection terminated unexpectedly" error the connection continues to fail with the error "Client has encountered a connection error and is not queryable".
Can you point me to some approach to handling this failing connection?
How can I detect this condition and how can I reconnect?
Maybe there's some configuration that is missing?
The text was updated successfully, but these errors were encountered: