[pgpool-general: 5936] Re: PgPool 3.7.2 forwards write statements to Standby

[Tatsuo Ishii]

No. Only 3.7.2 is affected by [1] since it tried to fix a problem
related to "ALWAYS_MASTER" which is new in 3.7.0.

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

> Will 3.6.9 and the other releases also have the same issue then or is this just a 3.7.2 problem?
> 
>> On Feb 27, 2018, at 7:45 AM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:
>> 
>> Not decided yet. I need to find a way to solve the original problem
>> which was supposed to be solved by [1].
>> 
>> Best regards,
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese:http://www.sraoss.co.jp
>> 
>>> Target date for 3.7.3?
>>> 
>>> 
>>> 
>>>> On Feb 27, 2018, at 7:26 AM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:
>>>> 
>>>> Today I have just found a serious regression in 3.7.2: it does not
>>>> work if the primary is other than node 0, sending write queries to
>>>> node 0, which is the standby (In my testing, 3.7.2 does work if the
>>>> primary is node 0). I guess your primary is not node 0, right?
>>>> 
>>>> The cause was this commit [1]:
>>>> https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=36517db60a829422d382debb7aa3256fac5da26d
>>>> 
>>>> So I today reverted the commit [2]:
>>>> https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e8baa3f0ee1a24f833cfa6cc5d0104b5cefe7b04
>>>> 
>>>> Until 3.7.3 is released, you could:
>>>> 
>>>> 1) Let node 0 to be the primary
>>>> 
>>>> 2) down grade to 3.7.1
>>>> 
>>>> 3) Apply the patch [2] to 3.7.2.
>>>> 
>>>> Sorry for the inconvenience.
>>>> --
>>>> Tatsuo Ishii
>>>> SRA OSS, Inc. Japan
>>>> English: http://www.sraoss.co.jp/index_en.php
>>>> Japanese:http://www.sraoss.co.jp
>>>> 
>>>>> Hello,
>>>>> 
>>>>> after updating the PgPool from 3.6.8 to 3.7.2 is is not working anymore.
>>>>> The “show pool_nodes” is showing the primary and standby correctly but it sends “Update” and “Select update” and others to standby. The workaround now is that we have disabled the standby-Postgresql.
>>>>> 
>>>>> Probably we will downgrade to the old version and check again.
>>>>> In parallel I try to find out what the Release Notes are telling about that. Maybe you can tell me how I can debug and find out what is happening there??
>>>>> 
>>>>> Mit herzlichen Grüßen
>>>>> 
>>>>> Mathias Buresch
>>>>> Systems Engineer
>>>>> -- 
>>>>> mathias.buresch at de.clara.net
>>>>> Tel: +49 (69) 40 80 18 - 265
>>>>> Fax: +49 (69) 40 80 18 - 129
>>>>> 
>>>>> Claranet GmbH
>>>>> Hanauer Landstraße 196
>>>>> 60314 Frankfurt
>>>>> 
>>>>> Geschäftsführung Olaf Fischer
>>>>> Hrb 50381 AG Frankfurt am Main
>>>>> Vat-ID de 812918694
>>>>> 
>>>>> http://www.claranet.de
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>> _______________________________________________
>>>> pgpool-general mailing list
>>>> pgpool-general at pgpool.net
>>>> http://www.pgpool.net/mailman/listinfo/pgpool-general