Charmander

I’d suggest creating a minimal reproducer script so it’s clear exactly what’s being measured, then translating it to C/libpq to get a better picture of how much of the issue...

(8.1.0 → 8.2.0 is when the entire protocol message parsing/serialization was rewritten into pg-protocol.) This probably isn’t related to the issue, but note that `Client#connect()` is asynchronous; to avoid involving...

@thedadow451 A PR would be great if you have it, yep! Thanks for investigating.

I’m a little surprised that multiple small *synchronous* writes to a `net.Socket` stream would translate to multiple TCP packets (as some comments above suggest happens), even with `TCP_NODELAY` set (which...

Are you using transactions anywhere? If you leave a client in an open transaction state without committing it or rolling it back before returning it to the pool, that transaction...

[Node 15](https://nodejs.org/docs/latest-v15.x/api/webcrypto.html#webcrypto_web_crypto_api) is correct. Even the version history on the Node 22 docs page mentions versions back to 16.

The pure JS library doesn’t support GSSAPI authentication (yet, as of 8.13.1).

See brianc/node-pg-types#78 for existing discussion about this. > We do not need native `BigInt` for data coming from the server, as in most cases the precision isn't needed. That’s not...

> @charmander From what I gather from the linked issue, there's a general consensus that it's a positive change (also I'm not sure why browsers are discussed there), is there...

@vitaly-t The current default is strings, not numbers, and correct/surprise-free behaviour is more important than small and avoidable performance differences anyway.