From: Jim C. Nasby <jnasby@pervasive.com>
To: PFC <lists@peufeu.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Marcos <mjs_ops@gmx.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Decide between Postgresql and Mysql (help of
Date: Tue, 28 Mar 2006 15:52:59 -0600
Message-ID: <20060328215259.GZ75181@pervasive.com> (raw)
In-Reply-To: <op.s642dpyecigqcu@apollo13>
References: <1143559902.1241.16.camel@servidor>
<1143572392.3625.79.camel@state.g2switchworks.com>
<op.s642dpyecigqcu@apollo13>
On Tue, Mar 28, 2006 at 09:42:51PM +0200, PFC wrote:
> However, throw in some maintenance operation which involves a long
> query with writes (like a big joined UPDATE) and all access to your
> website is blocked while the query lasts.
> This is worsened by the fact that MySQL sucks at complex queries.
>
> If all of your updates are done to a few rows, MyISAM is cool, but
> someday you'll want to do this query which locks a table during one
> minute... and then you got a problem.
Not to mention that MyISAM loves to eat data. Livejournal suffered at
least one major crash due to MyISAM corruption.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jnasby@pervasive.com, lists@peufeu.com, smarlowe@g2switchworks.com, mjs_ops@gmx.net
Subject: Re: Decide between Postgresql and Mysql (help of
In-Reply-To: <20060328215259.GZ75181@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox