[pgpool-general: 5934] Re: PgPool 3.7.2 forwards write statements to Standby
ishii at sraoss.co.jp
Tue Feb 27 22:45:00 JST 2018
Not decided yet. I need to find a way to solve the original problem
which was supposed to be solved by .
SRA OSS, Inc. Japan
> 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 :
>> So I today reverted the commit :
>> 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  to 3.7.2.
>> Sorry for the inconvenience.
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>>> 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
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
More information about the pgpool-general