Charmander
Charmander
I think the issue there might be not closing the `QueryStream`, although if it is, the error message and amount of error checking can definitely be improved.
The reason will have been emitted as an `'error'` event on the client (and on the pool as well, if you’re using a pool).
@GeorgeWL The original issue was closed with a fix. If you’re seeing something new or something that appears to be the same, please include details.
> The problem with exports in package.json is that it would require a major semver bump Seems appropriate enough? > unless we want to list all files manually there and...
@mriedem The fix applies to any long message.
> This requires knowing ahead of time whether the server supports TLS or not, even if we don't care about TLS. Not ruling out support, but: if you don’t care...
@ariofrio Batched queries – pipelining – is broader than batch insert. pg doesn’t have pipelining yet. I think @brianc is working on it. > I am planning to migrate a...
> You do not need to do the DNS lookup in javascript. The reason it’s done in JavaScript is that it’s blocking in libpq, IIRC.
@vitaly-t Isn’t this something the pure-JS library should have feature parity with?
@PavelPolyakov There’s a single PR that doesn’t contain the implementation of the feature.