node-postgres
node-postgres copied to clipboard
brianc
PostgreSQL client for node.js.
Is this possible using pure JavaScript `pg`? The `psql` accepts a URL like this where `libpq` figures out which of the IP addresses are still the read-write server: `postgres://192.168.70.20:5432,192.168.70.10:5432,192.168.70.30:5432/postgres?target_session_attrs=read-write` See...
Connection pools provide a query shortcut, which is convenient. It currently does not work with cursors though. Example (Typescript) code: ``` const pool = new Pool({ user: 'user', host: 'host',...
If a client of pg-cursor is closed mid query then other queries start to hang. ``` const Cursor = require('pg-cursor'); const {Pool} = require('pg'); const pool = new Pool({ connectionString:...
This re-adds in functionality that was broken in #2171 with regards to passing existing sockets into pg. This was causing things like SOCKS proxies to fail. Checks to see if...
```ts const connection1 = await pool.connect(); const connection2 = await pool.connect(); await connection1.end(); await connection2.end(); await pool.end(); ``` is giving `Error: Promise returned by test never resolved`
Hi. It seems that `min` parameter of Pool configuration is not used. **Code** ``` let pool = new Pool({ database: connectionConfig.database, port: connectionConfig.port, nolimit: connectionConfig.nolimit, user: connectionConfig.user, password: connectionConfig.password, host:...
https://github.com/brianc/node-postgres/blob/master/packages/pg/lib/sasl.js Line 23 to 25
fixes https://github.com/brianc/node-postgres/issues/2716 `client.end()` will resolve early if the connection is already dead, rather than waiting for an "end" event that will never arrive. This also makes `client.end()` resolve only when...
The node-postgres module frequently hangs when the PostgreSQL server restarts abruptly. The node-postgres package was working fine prior to pg version 8.7.1 as required by Node.js version 16. The two...
https://github.com/brianc/node-postgres/pull/2753 was merged 16 days ago Probably it is a good time for new npm release and we could use version with patches Also it fixed that issue https://github.com/brianc/node-postgres/issues/1105
