Le 31/03/2011 02:03, Sean Tegtmeyer a écrit :
Hi all,
In both master-slave mode and replication mode, pgpool-II is only running
on one box, correct?
If you only run pgpool on one box, yes, correct.
Therefore pgpool-II does not provide
a fail-over solution in the case that the box
My idea was, and I didn't test it, it's:
Server 1Server 2
postgres 9 A postgres9 B
pgpool A pgpool B
application A application B
The idea was :
- pgpool A is active, it's doing a streaming replication with postgres A and
B.
-application A is
I'm just trying to upgrade from 3.0.1 to 3.0.3.
Unfortunately, it complains like below:
Mar 31 23:16:09 db20 pgpool: 2011-03-31 23:16:09 ERROR: pid 22202:
pool_init_pool_passwd: couldn't open /etc/pool_passwd. reason: Permission denied
Mar 31 23:16:09 db20 pgpool: 2011-03-31 23:16:09 LOG: pid
On 31.03.2011 17:31, Tomasz Chmielewski wrote:
I'm just trying to upgrade from 3.0.1 to 3.0.3.
Unfortunately, it complains like below:
Mar 31 23:16:09 db20 pgpool: 2011-03-31 23:16:09 ERROR: pid 22202:
pool_init_pool_passwd: couldn't open /etc/pool_passwd. reason: Permission
denied
Mar
Hi all,
When adding in a new slave node to a running database cluster using
pgpool-II w/Postgres9.0 SR, we would need to add a new ***backend_hostname
*to the pgpool.conf, correct? Then would it be necessary to restart
pgpool-II as the pgpool-II manual suggests? I ask because I thought I
