Re: mysql to postgresql, performance questions - Mailing list pgsql-performance

From Dave Crooke
Subject Re: mysql to postgresql, performance questions
Date
Msg-id ca24673e1003211814q68616580h71b4987ef8a7bae2@mail.gmail.com
Whole thread Raw
In response to mysql to postgresql, performance questions  (Corin <wakathane@gmail.com>)
Responses Re: mysql to postgresql, performance questions
List pgsql-performance

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...

pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: mysql to postgresql, performance questions
Next
From: Craig Ringer
Date:
Subject: Re: GZIP of pre-zipped output