[pgpool-general: 5342] Will do_query() hangs after close message fix resolve idle in transaction problem

Avi Weinberg AviW at gilat.com
Sun Feb 19 23:49:57 JST 2017

Hi all,

I saw that pgpool had a fix related to do_query() hangs after close message.  I'm wondering if this fix might resolve the problem we have with idle in transaction.

Our idle in transactions is not postgres related since we tested it on several setups without pgpool and did not have it.  Only setups with pgpool have it.  We tested it on pgpool 3.5 and 3.6.

"Fix do_query() hangs after close message.

This is an en-bug in 3.6.1.

If an extend query appears right after a close message, do_query() is
called to check system catalogs, it hangs because it expects to read
pending data. This is caused by being mistakenly set the pending flag
after Close().

Back patch to 3.6-stable and 3.5-stable."
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170219/e9722890/attachment.html>

More information about the pgpool-general mailing list