Postgres queries running longer than statement_timeout

Question

I have statement_timeout set to 10000 (10 seconds) for a user in my Postgres database. However when I look at active queries in pg_stat_activity I find queries running for over 10 seconds (in some cases longer than 10 minutes). I set statement_timeout on the role executing these queries, and I have verified that in the pg_user table the user has statement_timeout=10000 set.

These statements are all inserts and I've verified there are no ungranted locks.

Why are these queries not being killed after the timeout?

Did you reload your config? With pg_reload_conf() function or restarting your db? — Abdel P.
– Abdel P., Commented Sep 26, 2018 at 2:18
Does "show statement_timeout" showing you the correct value? — Abdel P.
– Abdel P., Commented Sep 26, 2018 at 2:19

Gordon Seidoh Worley · Accepted Answer · 2018-09-26 02:19:50Z

6

It appears the issue is that the transactions are in the idle state (and since this is Postgres 10 I can further tell you the wait_event is ClientRead) and this means they are governed by a different timeout (although the documentation is ambiguous about this). The relevant config to set is idle_in_transaction_session_timeout.

answered Sep 26, 2018 at 2:19

Gordon Seidoh Worley

8,1367 gold badges51 silver badges90 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Postgres queries running longer than statement_timeout

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related