[pgpool-general: 4293] Re: Pgpool - connection hangs in DISCARD ALL
ishii at postgresql.org
Wed Jan 6 07:39:55 JST 2016
It's just an internal state flag and is not in pgpool.conf. The flag
represents whether user query is one of extended protocol messages.
SRA OSS, Inc. Japan
> I'm having this problem also. I looked at the bug fix " The fix is, resetting doing_extended_query_message flag in
> reset_query_list()." What does the mean? How do I enter the flag in pgpool.conf?
> -----Original Message-----
> From: pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] On Behalf Of Gerhard Wiesinger
> Sent: Tuesday, January 05, 2016 11:57 AM
> To: Tatsuo Ishii <ishii at postgresql.org>
> Cc: pgpool-general at pgpool.net
> Subject: [pgpool-general: 4291] Re: Pgpool - connection hangs in DISCARD ALL
> On 05.01.2016 15:25, Tatsuo Ishii wrote:
>>> On 04.01.2016 10:00, Tatsuo Ishii wrote:
>>>>>> On 31.12.2015 10:50, Tatsuo Ishii wrote:
>>>>>>>> Yes, reconfigured. Keep you up2date. Any fix for the logic possible?
>>>>>>> Yes, I'm thinking now.
>>>>>> Still hangs even with child_max_connections = 0, same stack trace.
>>>>> Too bad. I'm going to look for other causes if any.
>>>> I remebered this:
>>>> If you still have the problem after disabling client_idle_limit, the
>>>> fix is for you.
>> Sorry, I wanted to say:
>>> If you do not have the problem after disabling client_idle_limit,
>>> the fix is for you.
>>> Thnx, but still happens. Should I try master version or 3.3.7?
>> That's an option. However, if you like, could you try the fix before
>> going to 3.3? The patch may fix other code path which trigger the
>> problem. (or try 3.4-stable head).
> I tried the fix on the link already, but it didn't help (unless you did forget to attach another fix?).
> Will try 3.4-stable head, then 3.3 if it doesn't help.
> pgpool-general mailing list
> pgpool-general at pgpool.net
More information about the pgpool-general