Description
Hi @porsager !
Similar to #43, I'm also encountering similar ECONNRESET
errors with a PostgreSQL service on Render.com, but with a very low number of connections:
Apr 27 10:22:53 PM node:internal/process/promises:246
Apr 27 10:22:53 PM triggerUncaughtException(err, true /* fromPromise */);
Apr 27 10:22:53 PM ^
Apr 27 10:22:53 PM
Apr 27 10:22:53 PM Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:211:20) {
Apr 27 10:22:53 PM errno: -104,
Apr 27 10:22:53 PM code: 'ECONNRESET',
Apr 27 10:22:53 PM syscall: 'read'
Apr 27 10:22:53 PM }
Apr 27 10:22:54 PM error Command failed with exit code 1.
It seems like after a certain amount of time, the connection with PostgreSQL goes into this state where the ECONNRESET
errors start happening. Once it's in that state, it fails all queries for a while (a few minutes?). But then it eventually "wakes up" again (I guess Postgres.js eventually figured it out and reconnected at that point).
I'm using postgres@2.0.0-beta.5
- I'm assuming this beta version is not super unstable like this...? I never had any issues with this with Heroku's PostgreSQL service.
I've also asked for assistance from the Render.com support team over here: https://community.render.com/t/econnreset-with-node-js-and-postgresql/1498