On 2011-02-18T12:28:31, Jody McIntyre <[email protected]> wrote:
> I considered this, but unfortunately it would take a lot of effort. The
> existing "pgsql" resource agent is designed to start and stop postgres,
> whereas in this mode I want to switch an already running postgres into
> master mode. Even worse, once postgres is in master mode, there is no
> automated way to switch it back to standby mode (and writing one would
> require considerable effort.)
Well, you don't need it. I assume there's still a way to stop it,
though, and a failed demote will result in a stop.
So adding the master/slave functionality to the pg agent seems to make
sense still.
However, if there are fundamental conceptual problems with the m/s
implementation of our RA and the PG approach (and perhaps mysql?) we may
want to also extent the design of the m/s. Got any thoughts on that?
Regards,
Lars
--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Pacemaker mailing list: [email protected]
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
