Thanks Guys.
Since I use pgpool-II 3.0.4, I installed this function. and when I try to
recover the original primary which was down, it recovers, but comes up as
primary. It should actually be a standby, right?
I also the following line in pgpool.log:
Replication of node:1 is behind 67109104 bytes from the primary server (node:0)
It seems, I have done something wrong. Any clues here?
Thanks.
________________________________
From: Tatsuo Ishii <is...@sraoss.co.jp>
To: sandee...@yahoo.com
Cc: pgpool-general@pgfoundry.org
Sent: Saturday, September 17, 2011 1:40 PM
Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave
mode?
> I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used
> only in replication mode, and that too when somebody is using the
> failure/online recovery feature of pgPoll-II.
pgpool_walrecrunning is only usefull for streaming replication
mode in 3.0.x.
> At the same time, I found that this function has undergone some change:
> "
>
> Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the
> node that is promoted a primary node using the function. Now, pgpool-II waits
> for completing of the promotion to primary node because it did not work as we
> intended. But we still have a problem that pgpool-II waits while
> recovery_timeout, when there is no primary node(Kitagawa)
> "
>
> Can someone elaborate this please? Also, I assume that I need this function
> only when I setup pgPool-II in replication mode.
In pgpool-II 3.1 the function is not used anymore even in streaming
replication mode.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
_______________________________________________
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
