[pgpool-general: 9475] Re: Clarification on query results cache visibility

Achilleas Mantzios a.mantzios at cloud.gatewaynet.com
Thu May 8 20:07:47 JST 2025


On 5/8/25 07:49, Tatsuo Ishii wrote:

>> Good Day Tatsuo
>>
>> On 5/8/25 07:12, Tatsuo Ishii wrote:
>>
>>> In the mean time I have pushed v2 patch to all supported branches.
>>> https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=3f36fe3a39fe7c9cceec368d465506c7d1bc1c27
>>>
>>> As as the patch fixes the first problem without degradation like the
>>> second issue. I will watch the regression test results to see if the
>>> patch does anything bad.
>> Thank you, so you consider the patch to the second problem :
>> fix_bind.patch as a cause of degradation ?
> No I don't think so. I meant the first problem you reported (let it be
> "A") and the second problem you reported (let it be "B") are
> orthogonal. So I decided to push the v2 patch which fixed A.
>
> My plan is, I push the fix_bind.patch after you confirm it solves B.

So far, we haven't spotted any other problems, both bugs seem to be 
solved both by the automated java reproducer programs and in the real 
life tests.

So, from our standpoint, it would make sense to push fix_bind.patch as 
well, since it works correctly so far.

We are happy truly considering pgpool-II seriously for the first time 
(we are pgsql shop since 2001), so we will try to report anything we 
find along this journey !


>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS K.K.
> English:http://www.sraoss.co.jp/index_en/
> Japanese:http://www.sraoss.co.jp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20250508/ea66b4cd/attachment.htm>


More information about the pgpool-general mailing list