Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Client has encountered a connection error and is not queryable

See original GitHub issue

We are having error: Client has encountered a connection error and is not queryable

There is a suggestion to set idleTimeoutMillis: 0 https://github.com/brianc/node-postgres/issues/2512

How to do that using serverless-pg?

Issue Analytics

State:
Created a year ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

ddobryakredkneecommented, Sep 16, 2022

most probably this is the case. I will try to change the code accordingly

0reactions

MatteoGioiosocommented, Sep 16, 2022

It .connect and .clean should be used one time per lambda execution, at least that’s how I design it to work. Maybe is not really clear in the docs.

Top Results From Across the Web

"Client has encountered a connection error and is not ... - GitHub

1, we are getting "Client has encountered a connection error and is not queryable" error in production after a week of working just...

Node.js for some reason cannot connect to postgresql

The code crashes at the query object creation. var conString = "postgres://mydbusr:thepassword@localhost/mydb"; var client = new pg ...

postgres-pool - npm Package Health Analysis - Snyk

Node postgres connection pool implementation for node-pg For more information ... throws "Client has encountered a connection error and is not queryable" ...

"Client has encountered a connection error and is not ...

1, we are getting "Client has encountered a connection error and is not queryable" error in production after a week of working just...

Vincit/objection.js - Gitter

(node:25) UnhandledPromiseRejectionWarning: Error: Client has encountered a connection error and is not queryable at process.