node-pg-pool icon indicating copy to clipboard operation
node-pg-pool copied to clipboard

A connection pool for node-postgres

Results 32 node-pg-pool issues
Sort by recently updated
recently updated
newest added

If `Pool#end` happens between client initiate connection and receiving callback with error, `_endCallback` will be never called.

Implements feature request from https://github.com/brianc/node-pg-pool/issues/124 .

Based on https://github.com/brianc/node-pg-pool/pull/109 Adds a new force unlock timeout, which is by default disabled to stay backwards compatible. This timeout forcefully ends the client if a client was taken from...

When a connection is released back to the pool, the connection should be reset to a clean state. This should probably be done by running ```sql rollback; discard all; ```...

Fixing a case when release() is called for a broken connection. without this, the broken connection is returned to the idle pool and reused.

Unless there's a compelling reason to throw when a developer calls `client.release` more than once, I'd prefer to see `client.release` mutate itself into a `noop` the first time it's called...

(To preface: thank you for providing & maintaining this package! We make extensive use of it within npm. I'm proposing support for a feature here but I want to stress...

Hi team, I Want to create connection fail over for multiple endpoint in node-pg-pool. How can I achieve it. If one connetion fails it needs to connect to second.. don't...

I was trying to add some logging to understand lifecycle and I was wondering if I can log the beginning and ending of pool draining?

Hi Brianc, I have just a concern about how to specify the max size (min size) of Pool, mean an optimal number. I know it depends on the server configuration,...

question