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

[Achilleas Mantzios]

On 1/5/25 03:02, Tatsuo Ishii wrote:
>> update : the bug (this new bug) is not present prior to the first
>> patch. So the bug (the new one) is not present in plain vanilla :
>> pgpool-II-4.6.0 . Reverting both patches solves the issue with the new
>> bug which has most probably to do with an array function called
>> "first" :
> "first" is coming with the extension? I am not familiar with it.

This (and a couple of others I wrote back then)  is a C function written 
by me, when still intarray was not an extension, I mean before the 
extensions framework, sometime in 2004 or so. This is a simple C 
function which returns the first element of an array.

dynacom=# \df+ first
                                                                               List 
of functions
Schema | Name  | Result data type | Argument data types | Type | 
Volatility | Parallel |  Owner   | Security |    Access privileges     | 
Language | Source code |
Description
--------+-------+------------------+---------------------+------+------------+----------+----------+----------+--------------------------+----------+-------------+
-------------
public | first | integer          | integer[]           | func | 
immutable  | unsafe   | postgres | invoker  | postgres=X/postgres     +| 
c        | first       |

        |       |                  |                     |      | 
            |          |          |          | powerprom=X/postgres 
    +|          |             |

        |       |                  |                     |      | 
            |          |          |          | default_group=X/postgres 
|          |             |

(1 row)

dynacom=#


>
>> select defid, description from machdefs where first(parents)=214766150
>> order by description;
>>
>> I haven't been able to reproduce with SQL (from psql).
> Is it possible for you to create a java reproducer?
I will try.
>
>> Also reverting both patches, i.e. going back to plain vanilla
>> pgpool-II-4.6.0 solves this new bug, but re-introduces the previous (
>> with seeing stale and data and not invalidate data on table
>> testpgpool)
>>
>>>>>> Best regards,
>>>>>> -- 
>>>>>> Tatsuo Ishii
>>>>>> SRA OSS K.K.
>>>>>> English:http://www.sraoss.co.jp/index_en/
>>>>>> Japanese:http://www.sraoss.co.jp
>>>>> _______________________________________________
>>>>> pgpool-general mailing list
>>>>> pgpool-general at pgpool.net
>>>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>>> _______________________________________________
>>>> pgpool-general mailing list
>>>> pgpool-general at pgpool.net
>>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>>> _______________________________________________
>>> pgpool-general mailing list
>>> pgpool-general at pgpool.net
>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20250501/b0aa1b02/attachment.htm>