From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgre vs MySQL |
Date: | 2008-03-12 17:15:25 |
Message-ID: | 20080312171525.GG8328@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ivan Sergio Borgonovo wrote:
> On Wed, 12 Mar 2008 09:13:14 -0700
> paul rivers <rivers(dot)paul(at)gmail(dot)com> wrote:
>
> > For a database of InnoDB tables, people tend to replicate the
> > database, and then backup the slave (unless the db is trivially
>
> That recalled me the *unsupported* feeling I have that it is easier
> to setup a HA replication solution on MySQL.
Well, if you have a crappy system that cannot sustain concurrent load or
even be backed up concurrently with regular operation, one solution is
to write a kick-ass replication system.
The other solution is to enhance the ability of the system to deal with
concurrent operation.
We keep hearing how great all those Web 2.0 sites are; Slashdot, Flickr,
etc; and they all run on farms and farms of MySQL servers, "because
MySQL replication is so good". I wonder if replication is an actual
_need_ or it's there just because the other aspects of the system are so
crappy.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2008-03-12 17:19:52 | Re: PostgreSQL user documentation wiki open for business |
Previous Message | Andreas 'ads' Scherbaum | 2008-03-12 17:11:50 | Re: PostgreSQL user documentation wiki open for business |