On Wed, Feb 27, 2019 at 7:56 AM Jeremy Finzel <finzelj@xxxxxxxxx> wrote:
I was hoping to use idle_in_transaction_session_timeout to prevent schema change migrations from running too long and thereby locking up the application for an extended period even if any one statement in the migration is very short.
I don't think you are actually going idle. Check pg_stat_activity for what this transaction is doing. It should show waiting on locks, but not idle. I think the command you seek is
SET lock_timeout TO '1s';
