Brian Lauber

FYI: It looks like you can trigger the issue one layer deeper as well. Ex: ``` // Added the `.stream` portion here c1.connection.stream.end(); ```

@brianc : Here's a variation on the earlier script that provides some more evidence around the issue: ``` const {Pool} = require('pg'); function delay(t) { return new Promise(function(resolve) { setTimeout(resolve,...

@sehrope : Right. The purpose of the code snippet was to recreate a scenario where the low-level socket was being closed/ended outside of the Pool's managed lifecycle. So, you're correct:...

@sehrope : Agreed -- there is always a race condition betw/ the handoff and the usage. But, based upon what has been reported, it seems that the Client/Connection has already...

@jpike88 : Out of curiosity, what are the main pain points you encounter when using the "2 separate Knex pools" approach? Ex: I'm guessing that this approach becomes problematic when...

@Frolanta : Just want to make sure I understand the problem you described above. On the AWS side: it rotates the replicate IP once per second. However, `knex` has a...

@Frolanta : Got it. So yeah: it sounds like we're on the same page, then. The reason I was asking: I've been experimenting w/ some redesigns around Knex's Transaction and...