[pgpool-general: 5562] Re: How to find what caused queries to get stuck

Tatsuo Ishii ishii at sraoss.co.jp
Wed Jun 7 12:02:30 JST 2017

Without fully understanding Pgpool-II source code, it would be pretty
hard to find the cause of stuck. Instead, I recommend you help
developers to provide enough information so that they can tackle on
it. i.e.

- Pgpool-II version
- pgpool.conf
- Pgpool-II debug log
- Self contained test case

Especially the last one is very important.

Best regards,
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php

> Hi all,
> We are using postgres 9.6 and 9.7 with pgpool 3.6.3.
> On setups using pgpool every so often we see "stuck" queries that are shown as idle in transaction.  Other setups that skip pgpool and connect directly to postgres never get those idle in transaction queries.
> We got to a point where we are forced to monitor our database and kill queries that are idle for more than x minutes, but obviously  we cannot keep it this way.
> How can I find what cause those queries to get stuck?
> Thanks
> Avi
> IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.

More information about the pgpool-general mailing list