[Pgcluster-general] MasterDB is always the first node from pgreplicate.conf - even if not accessible

Alexey Kamenchuk akamenchuk at topdog.uk.net
Mon Feb 19 06:49:40 UTC 2007


Hi All

 

I have 3 DB nodes in my cluster which are listed in Cluster_Server_Info list
as db1, db2, db3 (in exactly this order) in pgreplicate.conf

 

If I start db in recovery mode ( -R option ), replicator always tries to use
db1 as Master DB, it does want to use any other. For example if db1 is
stopped, db is running and I start db3 in recovery mode, I want it to synch
with db2, but it doesn't do this - it wait for db1 to be available

 

Looks like Master DB in recovery process is always the first node in
Cluster_Server_Info list. 

 

Is there a way to force recovery from another node when first one is not
running?

 

Thanks

 

Best regards

Alexey Kamenchuk

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/pgcluster-general/attachments/20070219/3357ff9b/attachment.html 


More information about the Pgcluster-general mailing list