[pgpool-general: 5916] Re: Query got stuck when running Vacuum
ishii at sraoss.co.jp
Sun Feb 11 17:00:55 JST 2018
Then this may be the cause of Pgpool stuck. This was found pretty
recently (thus after 3.6.8):
BTW we are going to release 3.6.9 on Feb 13 which will include the fix
SRA OSS, Inc. Japan
> We are using the latest version 3.6.8.
> -----Original Message-----
> From: Tatsuo Ishii [mailto:ishii at sraoss.co.jp]
> Sent: Friday, February 09, 2018 1:25 AM
> To: Avi Weinberg <AviW at gilat.com>
> Cc: pgpool-general at pgpool.net
> Subject: Re: [pgpool-general: 5913] Query got stuck when running Vacuum
>> Hi all,
>> We saw that one of our queries got stuck with idle in transaction.
>> The log showed the following message
>> terminating connection due to conflict with recovery User query might
>> have needed to see row versions that must be removed.
>> Probably vacuum ran at the same time and that what caused it.
>> I saw in pgpool FAQ that "hot_standby_feedback = on" can be used.
>> Will this ensure that no queries will get stuck because of vacuum?
>> Will setting the parameter to true cause more traffic between the two nodes or slow down things?
>> Why pgpool does not pass this error instead of having the query stuck?
> Well, pgpool stuck is different story from recovery conflict. Up to now there have been several commits that fix stuck problems. So what your pgpool version exactly?
> Best regards,
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> 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