Yeah, if there's one thing I've learned looking for database stuff it's that PostgreSQL and MySQL have strong supporters on both sides. I'm not looking to create a war either. My concern from what LITTLE I know is that it sounds like there's less support/compatibility for PostgreSQL and it's maybe a little more complicated? This being my first real foray into the whole database thing in general I'm trying to find the simplest/sturdiest/best supported way in. Am I making PostgreSQL seem harder than it is for a Newb? Or am I better off sticking with MySQL?
Levi (: -Not trying to start a war here... On Wednesday 10 August 2005 3:11 pm, Andrew Lentvorski wrote: > Levi Smith wrote: > > The > > question is, once I start getting a database out there, what's the best > > method for keeping them synchronized? > > If you are starting to look at high availability stuff, you probably > want to start looking at PostgreSQL as well as MySQL. > > http://www.taygeta.com/ha-postgresql.html > > Synchronization, locks, atomicity, etc. are areas where PostgreSQL and > MySQL have actual differences. > > Please note that I did *NOT* declare one of them better than the other. > I don't currently have the time for a religious flamewar. > > -a -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
