Re: MySQL and PG (was Dr. Miguel....)
Re: MySQL and PG (was Dr. Miguel....)
- Subject: Re: MySQL and PG (was Dr. Miguel....)
- From: Andrew Lindesay <email@hidden>
- Date: Fri, 4 Dec 2009 16:50:08 +1300
Hello Guido;
I have to concur; PG has been really great for me and I have had some problems with MySQL. The most serious problem with MySQL was memory-exhaustion in the driver, but the latest MySQL driver has seemed to _finally_ resolved that one. I have to also concur with Mike though in that I did try to take pgpool (replication only) to a production environment and it was not a happy morning and I had to roll it back. If I had to choose between the two for a small WOA, I would definitely lean towards PG because of the trouble-free operations I've experienced. I notice there are a number of companies offering support for larger PG deployments.
cheers.
> I don't think I ever used MyISAM tables with a WO app. I have seen corrupted data with InnoDB tables and WO usage though. For the rest, they might have been MyISAM used from some PHP web crap, but the thing is: the SQL stored the thing and some historic data gets corrupted. That was the issue we had. I can't recall exactly enough to blame it completely on MySQL, but I stopped using it and I had never ever again any issues with corrupt data (95% PostgreSQL, 5% FrontBase usage).
>
> FrontBase has the issue that you can easily kill the server with bad input. This can't happen with PostgreSQL as you get your own backend for each connection.
>
> Between the three databases MySQL, PostgreSQL, and FrontBase, I've used PostgreSQL the most and with the most success and least amount of trouble. I'd love to see a multi master clustering solution for it though that actually works and is not a piece of shit.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden