From: Dave Crooke <dcrooke@gmail.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: pgsql-performance@postgresql.org, Corin <wakathane@gmail.com>
Cc: Andy Colson <andy@squeakycode.net>
Subject: Re: mysql to postgresql, performance questions
Date: Sun, 21 Mar 2010 20:14:19 -0500
Message-ID: <ca24673e1003211814q68616580h71b4987ef8a7bae2@mail.gmail.com> (raw)
In-Reply-To: <ca24673e1003211813jb05529ex33e02bcc304fbab0@mail.gmail.com>
References: <4BA23936.2030507@gmail.com>
<4BA596D2.4050406@squeakycode.net>
<b42b73151003211543w764cfb9bwe3666671310b875a@mail.gmail.com>
<ca24673e1003211813jb05529ex33e02bcc304fbab0@mail.gmail.com>
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...
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: dcrooke@gmail.com, mmoncure@gmail.com, wakathane@gmail.com, andy@squeakycode.net
Subject: Re: mysql to postgresql, performance questions
In-Reply-To: <ca24673e1003211814q68616580h71b4987ef8a7bae2@mail.gmail.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