We're moving from MySQL to PG, a move I am rather enjoying, but we're
currently running both databases. As we web-enable our financial
services in fifteen countries, I would like to recommend the team that
we move entirely to PG.
In doing research on big installations of the two databases, I read
this from a MySQL senior exec on Slashdot:
QUOTE---
"...We did it ourselves with MySQL Cluster. That's technology
originally developed by Ericsson - and today it is an absolute
category leader in telco and networking. Nokia, Alcatel and Nortel are
all building real-time network nodes on top of MySQL Cluster. No one
else has a main-memory based shared-nothing cluster with that high
throughput and availability. Or take the new Monitoring and Advisory
Service that we are launching as part of MySQL Enterprise - this is a
novel innovatoin built on the feedback from our most advanced users
and customers."
--UNQUOTE
The sentence that caught my attention is "Nokia, Alcatel and Nortel
are all building real-time network nodes on top of MySQL Cluster."
My experiences with MySQL so far have been less than exhilerating
(only tried it for our web stuff, which is not much so far but
increasingly rapidly) but I have seen a lot of talk about MySQL
clusters.
Is there something similar in the PG world? PG Clusters?
Google search comes up (apart from the "cluster" command) with stuff
like this in the mailing list archives -- http://snipr.com/1pxkf --
which I am not sure is very heartening piece of news.
I'd appreciate any thoughts or experiences, or starting points for
what I should start reading in terms of PG in high availability
situations, including replication and whatnot. Am I speaking of
something like "EnterpriseDB" (is that Postgresql with tech support,
or a different DB?)
TIA!