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

Hi there, I got some issues with this pool. Maybe this is related to https://github.com/brianc/node-postgres/issues/1790 and https://github.com/brianc/node-postgres/issues/1611. First of all this is my environment: - [email protected] - [email protected] - NodeJS...

fix #132 more useful than only processing the current active connection queries with end() is to finish processing all current pending queries before shutting down and calling the callback, so...

Greetings everyone, I believe the documentation for `pool.on('error')` is inaccurate/incomplete. The documentation directs users to "handle this in the same way you would treat process.on('uncaughtException')". The [uncaughtException event](https://nodejs.org/api/process.html#process_event_uncaughtexception) discourages users...

pool.end() processes the queries in the active connections but then drops all other pending queries, there really needs to be an option to also process all pending queries or end()...

The pool.end callback/promise should resolve after the last pool.query finishes but that doesn't happen: ``` pool.query(query).then(() => console.log('done')) pool.query(query).then(() => console.log('done')) pool.end().then(() => console.log('end')) ``` result: ``` done end done...

bug

Currently the pool only tracks total clients and pending connections. It would be extremely useful to be able to know how many clients are checked-out (active) at any given time,...

数据库设计字段类型为:int8,通过查询返回字段值是字符串类型了?why

- `standard-format` removed (deprecated, `standard --fix` should be used) - `standard` updated to `14.1.0` (and 3 new lint errors fixed) - `test` scripted splitted to `unit` & `test` Steps for...

This is a request for comments, feedback welcome. If a client is not queryable, the pool should prevent requeuing instead of strictly enforcing errors to be propagated back to it....

In the _remove routine when client.end is called we are seeing frequent throws because the socket has already been closed. We wrapped the call to client.end in a try catch...