Charmander
Charmander
Is it possible to include a test?
You should be able to write the test by making a `net.Server` that does nothing with the client it accepts but call `pool.end()` and close the connection. There are a...
pg was created before a JavaScript primitive that could represent 64-bit integers precisely existed, but you can [change the parser][pg-types] to produce a `BigInt` nowadays: ```js const types = require('pg').types;...
@coderholic Unless it’s an unhandled error you expect to be handled by `pool.query()`, no, it’s not related to #131. It doesn’t sound like the same issue as this issue, either,...
@coderholic Okay, that different error message is caused by a timeout acquiring a client when there’s no room left in the pool to connect new ones. I don’t know what...
> If I'm understanding correctly, this error is about queued queries timing out while waiting for a connection to the DB to be returned to the pool, it's not actually...
@ThisIsMissEm Is that PR blocked on this? It looks more like it would be made unnecessary by this.
@ThisIsMissEm On second read, it looks like the Mastodon PR is necessary either way. Unless you were planning on deleting all of that code if this were merged and released...
@tleiroblox Was there some kind of pathological date case that I missed? 3x speedup on parsing doesn’t sound like “serious performance issues”.
@mgabeler-lee-6rs Probably not controversial. I think attaching a no-op error listener to the pool by default has already been proposed, and is the most likely change? Queries erroring with the...