[Pgcluster-general] Best practice for bringing up clustered DBs
Tarhon-Onu Victor
mituc at activemediatech.com
Thu Feb 22 14:41:24 UTC 2007
On Thu, 22 Feb 2007, Leif Madsen wrote:
> Then, on the other clustered DBs, to do something like:
>
> ./bin/pg_ctl start -D /usr/local/pgsql/data -o "-U"
>
> I've not had any luck with -R so far, and -r actually returns an error
> for me. Perhaps I'm not using those flags in the correct scenarios?
> (If someone would like to expand upon when to use -r, -R, and -U,
> that'd be very helpful.)
Probably you were not so lucky with -R because you haven't set up
rsync correctly (or ssh, or anything else involved) :) ...because that's
the way I'd recommend to replicate the database on the other cluster
members.
P.S.: I'm very happy that there are a lot other people testing too, I've
been waiting for a pgcluster patch for the latest postgresql version quite
long, and now that I have it the only thing that prevents me from moving
pgcluster into production is a little thing like, the first cluster member
listed in pgreplicate.conf is considered always to be the master and if
that one goes down, when I try to synchronize it pgreplicate tries to
connect to the same cluster member (although there are some keepalives
flying around).
--
Victor Tarhon-Onu
Lead Systems Administrator
ActiveMedia Technology
http://www.activemediatech.com
.............................................................................
This communication contains information that is confidential and may also be
privileged. It is for the exclusive use of the intended recipient(s). If you
are not the intended recipient(s) please note that any form of distribution,
copying or use of this communication or the information in it is strictly
prohibited and may be unlawful. If you have received this communication in
error kindly notify the sender immediately and delete it from your system.
More information about the Pgcluster-general
mailing list