[pgpool-general: 4069] Re: Postgres Sequence numbers different on backends when inserts run concurrently

[Tatsuo Ishii]

I think he has committed the fix already in git repository and you can
grab it as a patch.

http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=43ff7d3de9db4c8a1143258f4ffff98682dab560

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

From: Steve Kuekes <steve.kuekes at physicianspharmacy.com>
Subject: [pgpool-general: 4062] Re: Postgres Sequence numbers different on backends when inserts run concurrently
Date: Mon, 14 Sep 2015 16:44:13 -0400
Message-ID: <55F7319D.2010002 at physicianspharmacy.com>

> Yugo,
> 
> Is there an update on this patch.  update to the latest pgpool
> version.
> 
> Steve
> 
> On 07/30/2015 04:15 AM, Yugo Nagata wrote:
>> On Tue, 28 Jul 2015 13:40:14 +0900
>> Yugo Nagata <nagata at sraoss.co.jp> wrote:
>>> I'll look into this and fix it.
>> I found that insert-lock never be issued at 3.4.3. The problem is
>> the following commit:
>>
>> "Fix the case when user table includes spaces"
>> http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=6a7b1ff4eb1cf0fba16ff3ca909a1505355b05ae
>>
>> Due to this, table names passed to pgpool_regclass are double-quoted
>> and pgpool_regclass('"public.my_table"') always returns null. Instead,
>> it should be pgool_regclass('"public"."my_table"').
>>
>> This causes pgpool-II to fail to check needs for insert_lock properly.
>>
>> I'll make a patch for fixing it.
>>
> 
> -- 
> Steve Kuekes
> 
> Physicians Pharmacy Alliance
> 118 MacKenan Drive, Suite 200
> Cary, NC  27511
> 919-465-5801 direct
> 919-463-5555 main
> 919-463-5566 fax
> 
> steve.kuekes at physicianspharmacy.com
> 
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general