Knex 3.x pool configuration: idle connection eviction versus database-side TCP timeouts
Goal I am configuring the Knex.js connection pool (backed by tarn.js) for a service where the database server drops idle TCP connections aggressively. The goal is to ensure that a connection handed out from the pool is never one the server has already closed, without over-evicting healthy idle connections. Constraints and uncertainty Knex exposes pool.min ,
knexjs