Skip site navigation (1) Skip section navigation (2)

Re: Decide between Postgresql and Mysql (help of

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: PFC <lists(at)peufeu(dot)com>
Cc: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Marcos <mjs_ops(at)gmx(dot)net>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Decide between Postgresql and Mysql (help of
Date: 2006-03-28 21:52:59
Message-ID: 20060328215259.GZ75181@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-performance
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(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

In response to

pgsql-performance by date

Next:From: Jim C. NasbyDate: 2006-03-28 21:56:08
Subject: Re: Decide between Postgresql and Mysql (help of
Previous:From: PFCDate: 2006-03-28 21:24:28
Subject: Re: Decide between Postgresql and Mysql (help of

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group