We're hitting an issue in sequelize when using postgres's idle_in_transaction_session_timeout.
When the code inside a transaction hits the timeout it causes the connection to be destroyed due to a protocol error and waiting connections throw a ConnectionAcquireTimeoutError after 60s (the default acquireTimeoutMillis in sequelize).
We're hitting an issue in sequelize when using postgres's
idle_in_transaction_session_timeout
. When the code inside a transaction hits the timeout it causes the connection to be destroyed due to a protocol error and waiting connections throw aConnectionAcquireTimeoutError
after 60s (the defaultacquireTimeoutMillis
in sequelize).It's easily reproducible using
pool.max: 1
and:Resolves to:
Expected behaviour would be for the second query to be fulfilled.