Re: Justifying a PG over MySQL approach to a project

How difficult is it to switch the master's hat from one DB instance to another?  Let's say the master in a master-slave
scenariogoes down but the slave is fine.  Can I designate the slave as being the new master, use it for read/write, and
thenjust call the broken master the new slave once it comes back to life (something like that)? 



-----Original Message-----
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Greg Sabino Mullane
Sent: Thursday, December 17, 2009 9:28 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Justifying a PG over MySQL approach to a project


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> - MySQL is horizontally scalable via clustering and multi-master
> replication (though you must beware of numerous gotchas). PostgreSQL can
> be used with read-only slaves via Slony/Bucardo/etc replication, but is
> limited to a single authoriative master.
>
> (There's work ongoing to enable readonly hot standby slaves with
> failover, but no multi-master is on the horizion).

Well that's refreshing: usually Bucardo is mistaken for a system that
only does master-master and not master-slave, rather than vice-versa. :)
You can have two authoritative masters with Bucardo, in addition to
any number of slaves radiating from one or both of those (as well as
just simple master->slaves).

> - It's a cool tool when you want to query and integrate data from all
> sorts of disparate sources, thanks to its support for pluggable storage
> engines. If you want something for data analysis and integration rather
> than safe storage it's well worth looking at.

What sort of sources? I'm curious here to find areas we can improve upon.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 200912170927
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAksqP9kACgkQvJuQZxSWSshbUQCg3CfvpeivDi6gg2bkr74I17Qe
RKAAnRu3GTUQ3Bg3R2Fq3eOsgK4N0xd1
=5r9R
-----END PGP SIGNATURE-----



--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general