Postgres Timeout For Statements

[Samuel Reh]

I have a problem where some of my queries run way too long. Obviously, the
long term solution is to fix the slow queries, but for now I'd like to use
some sort of timeout for when this happens. Currently I log in and run
`select pg_terminate_backend(pid)`.

I'm using the PG gem and the Threaded connection pool.

Is there a way for Sequel to kill these connections (or better yet, put
them in an idle state so they become available in the pool)? Or should I be
using pg_bouncer for this kind of stuff?

Thanks,
Sam

[Jeremy Evans]

Post by Samuel Reh
I have a problem where some of my queries run way too long. Obviously, the
long term solution is to fix the slow queries, but for now I'd like to use
some sort of timeout for when this happens. Currently I log in and run
`select pg_terminate_backend(pid)`.
I'm using the PG gem and the Threaded connection pool.
Is there a way for Sequel to kill these connections (or better yet, put
them in an idle state so they become available in the pool)? Or should I be
using pg_bouncer for this kind of stuff?

PostgreSQL supports setting a statement timeout per connection, so you can
use an after_connect proc to set it for all connections that Sequel creates:

DB = Sequel.connect('postgres://...', :after_connect=>proc{|c|
c.execute('SET statement_timeout = 1000')}) # one second

Thanks,
Jeremy