[pgpool-general: 5693] Re: Postgres error not processed by pgpool
ishii at sraoss.co.jp
Wed Aug 9 19:10:05 JST 2017
Forwarding to the mailing list.
SRA OSS, Inc. Japan
From: Tatsuo Ishii <ishii at sraoss.co.jp>
Subject: Re: [pgpool-general: 5683] Postgres error not processed by pgpool
Date: Sat, 05 Aug 2017 05:55:11 +0900 (JST)
Message-ID: <20170805.055511.2064995071833270919.t-ishii at sraoss.co.jp>
> Thanks for quick test and report!
> Best regards,
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
>> I got around to building from HEAD and I just wanted to confirm to you that
>> the two problems I've been having (segfaulting and error not returned) are both fixed there.
>>> -----Original Message-----
>>> From: Tatsuo Ishii [mailto:ishii at sraoss.co.jp]
>>> Sent: Thursday, August 03, 2017 4:16 PM
>>> To: Jeremiah Penery
>>> Cc: pgpool-general at pgpool.net
>>> Subject: Re: [pgpool-general: 5683] Postgres error not processed by pgpool
>>> > I'm using Pgpool-II 3.6.5 with Postgres 9.6.3, and seeing issues sometimes
>>> when a SQL statement generates an error in Postgres, that the Pgpool
>>> process seems to wait forever for some kind of response. This causes
>>> application code to hang as well.
>>> > I'm attaching logs from both Pgpool and Postgres (the configuration here is
>>> one machine, everything co-resident). I can get more logging information or
>>> anything else if necessary. The issue is easily reproducible, though I don't
>>> think it happens 100% of the time.
>>> > Thanks,
>>> > Jeremiah
>>> That could be already fixed by this recent commit:
>>> Best regards,
>>> Tatsuo Ishii
>>> SRA OSS, Inc. Japan
>>> English: http://www.sraoss.co.jp/index_en.php
More information about the pgpool-general