[pgpool-general: 8811] Re: queries not redirecting to primary when "delay_threshold_by_time" is exceeded

[Tatsuo Ishii]

>> > I will look into this.
>>
>> It turned out that delay_treshold_by_time is broken since it was introduced.
>> I have fixed it and pushed to the git repository.
>> https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=6aebf24aa9a627f4c852e44f6407f17a34d50528
>>
>> Unfortunately there's no workaround of this for now. Please use
>> delay_treshold instead if you like.
> 
> Thanks for looking into this.
> This is really impacting us a lot - Is it possible to have a 4.4.4
> release with this fix?

Yes, 4.4.4 will have the fix.

> According to the site, next release is slated for August 17th, 2023
> (more than two months away)

Yes, that's our plan.

> and using delay_treshold is not not really an option for us due to
> business requirements (one cannot "translate" amount of WAL bytes to
> replication lag "time")

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp