Charmander
Charmander
@Andrei-Stepanov That sounds like an issue separate from what this PR claims to address (and what I was requesting a test case for), then. Please open an issue for it.
`min` doesn’t exist. I don’t think `nolimit` does either.
There’s probably something to fix here, but note that you shouldn’t call `.end()` on connections acquired from a pool – just `.release()` or `.release(true)`.
@mauritsl You didn’t connect that client. `await client.connect();`
> The reason why your solution "seems to work" is because you never actually ended the client session and released it back to the running pool. @Animadei `client.release()` releases the...
@rpominov Check if it’s missing before making a connection attempt.
You need to attach an `error` listener to the pool. It doesn’t have to do anything (could just be `poolInstance.on('error', console.error)`). The behavior is expected, but not good.
Ah, also don’t do this and throw away the connection: ```js databaseConnectionPool .connect() ``` (`connect()` doesn’t initialize the pool, it’s how you request a client from the pool.)
[no](https://node-postgres.com/features/pooling#examples)