node-postgres
node-postgres copied to clipboard
brianc
PostgreSQL client for node.js.
After have updated from 5.1 to 6.2.4, I see sometimes (nearly once a day) the following error which crashes our production server : ```bash Error: Connection terminated unexpectedly 2017-06-15T10:03:33.683+02:00 at...
In preparation for v3.0.0, we start warning users to be explicit about the sslmode they want.
Not sure there is anything to be done in the PG library but any tips in regards to investigating this issue further would be welcome. We connect to a NEON...
https://github.com/brianc/node-postgres/blob/9bfc967e91d4c347d7a58f0f3732c2514f272afa/packages/pg-protocol/package.json#L7-L18 It seems that by adding the new "exports" flags to `package.json`, now when compiling anything depending on `pg` (and relatively `@types/pg`) using the `bundler` module resolution fails with: ```...
When query with cursor, following code will crash. ```js import { Pool, PoolClient, escapeIdentifier } from 'pg'; import Cursor from 'pg-cursor'; const dbConfig = parse('postgresql://postgres@localhost/postgres'); const pgPool = new Pool({...
_TL;TR: pg seems fast!_ Hi, I've made a small benchmark to compare this library against others that claim to be the fastest: [Postgres.js](https://github.com/porsager/postgres) and [Bun.SQL](https://bun.sh/docs/api/sql). Inspired by some online benchmarks,...
Hi! I got a bug report in pgkit which uses pg/lib/type-overrides: https://github.com/mmkal/pgkit/issues/443 It seems to be because of the new `exports` definition on package.json Here's an easy repro you can...
Hi @voodootikigod @jeremyevans @dmnd @pshc @mikl are you planning to migrate completely to TypeScript ? If not I can raise a pull request for this as a contribution. Thanks!
Roadmap for the 3.0.0 version of pg-connection-string Proposed changes: - use libpq semantics for sslmode - remove `no-verify` option - only accept libpq compatible query parameters - https://github.com/brianc/node-postgres/issues/1095 - support...
Currently `pg-connection-string` only have a unserialize method `parse` . On some use cases, I want to construct a connection object and serialize to a string. So it could be better...
