Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id EBD80634ED1
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Sun, 21 Mar 2010 22:14:31 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia,
	port 10024) with ESMTP id 53689-08
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Mon, 22 Mar 2010 01:14:20 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-bw0-f221.google.com (mail-bw0-f221.google.com
	[209.85.218.221])
	by mail.postgresql.org (Postfix) with ESMTP id 2E5A8634EC3
	for <pgsql-performance@postgresql.org>;
	Sun, 21 Mar 2010 22:14:21 -0300 (ADT)
Received: by bwz21 with SMTP id 21so4847350bwz.35
	for <pgsql-performance@postgresql.org>;
	Sun, 21 Mar 2010 18:14:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type;
	bh=d62KI/L64WEVuGWL6XCI+9wAX8h+89UJPsyKbKyVX6M=;
	b=tncn2u6OdK4bg/Pb0PEpSJgqNHOzUCyXzoRJXDW5TAIEgT10NUlzUeFDgzh+3ul9AX
	70x/y9BbMs4vJ4y7DqJ0AnFL3qviZdk0f6nOh7CPVOa4NGCL8aVlXRWG4CzaWlbfYgj1
	wSwFn0VOaiw/lvJwGwnZv1GVa/svegj3oW3u0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=JG4QkEAieQXnVpD0aXAzS2O7q1vrK9vZbKIh6aMAtcvbpqN22hNR8eNVBuRmQXSPeL
	AowfXJ1qFgEPIUrrkNaWgSC7SKRJJxhDAO5t92W7j+onnpc0szOXXyJFyqhmHvQfTkMf
	PZ2hHfDAVo4O3oWtYmBvVv+E4GvEP2M74dOsg=
MIME-Version: 1.0
Received: by 10.204.135.154 with SMTP id n26mr7840100bkt.18.1269220459129;
	Sun, 21 Mar 2010 18:14:19 -0700 (PDT)
In-Reply-To: <ca24673e1003211813jb05529ex33e02bcc304fbab0@mail.gmail.com>
References: <4BA23936.2030507@gmail.com> <4BA596D2.4050406@squeakycode.net>
	<b42b73151003211543w764cfb9bwe3666671310b875a@mail.gmail.com>
	<ca24673e1003211813jb05529ex33e02bcc304fbab0@mail.gmail.com>
Date: Sun, 21 Mar 2010 20:14:19 -0500
Message-ID: <ca24673e1003211814q68616580h71b4987ef8a7bae2@mail.gmail.com>
Subject: Re: mysql to postgresql, performance questions
From: Dave Crooke <dcrooke@gmail.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org, Corin <wakathane@gmail.com>,
	Andy Colson <andy@squeakycode.net>
Content-Type: multipart/alternative; boundary=00151747af0a9baab60482596a31
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5
	tests=BAYES_00=-2.599, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 201003/263
X-Sequence-Number: 38088

--00151747af0a9baab60482596a31
Content-Type: text/plain; charset=ISO-8859-1

Note however that Oracle offeres full transactionality and does in place row
updates. There is more than one way to do it.

Cheers
Dave

On Mar 21, 2010 5:43 PM, "Merlin Moncure" <mmoncure@gmail.com> wrote:

On Sat, Mar 20, 2010 at 11:47 PM, Andy Colson <andy@squeakycode.net> wrote:
> Don't underestimate my...
for non trivial selects (myisam has no transaction overhead so can
usually edge out pg in row by row ops), and without taking multi user
issues into account, it's often going to come down to who generates a
better plan.  postgres has more plan options and a better statistics
model and can usually beat mysql on many types of selects.

updates w/myisam are where mysql really shines in single user apps.
the reason is obvious: no mvcc means the heap can often be updated in
place.

merlin


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to y...

--00151747af0a9baab60482596a31
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>Note however that Oracle offeres full transactionality and does in place=
 row updates. There is more than one way to do it.</p>
<p>Cheers<br>
Dave</p>
<p><blockquote type=3D"cite">On Mar 21, 2010 5:43 PM, &quot;Merlin Moncure&=
quot; &lt;<a href=3D"mailto:mmoncure@gmail.com">mmoncure@gmail.com</a>&gt; =
wrote:<br><br><p><font color=3D"#500050">On Sat, Mar 20, 2010 at 11:47 PM, =
Andy Colson &lt;<a href=3D"mailto:andy@squeakycode.net">andy@squeakycode.ne=
t</a>&gt; wrote:<br>
&gt; Don&#39;t underestimate my...</font></p>for non trivial selects (myisa=
m has no transaction overhead so can<br>
usually edge out pg in row by row ops), and without taking multi user<br>
issues into account, it&#39;s often going to come down to who generates a<b=
r>
better plan. =A0postgres has more plan options and a better statistics<br>
model and can usually beat mysql on many types of selects.<br>
<br>
updates w/myisam are where mysql really shines in single user apps.<br>
the reason is obvious: no mvcc means the heap can often be updated in<br>
place.<br>
<font color=3D"#888888"><br>
merlin<br>
</font><p><font color=3D"#500050"><br>-- <br>Sent via pgsql-performance mai=
ling list (<a href=3D"mailto:pgsql-performance@postgresql.org">pgsql-perfor=
mance@postgresql.org</a>)<br>To make changes to y...</font></p></blockquote=
>
</p>

--00151747af0a9baab60482596a31--