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

Re: mysql to postgresql, performance questions

From: Dave Crooke <dcrooke(at)gmail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, Corin <wakathane(at)gmail(dot)com>, Andy Colson <andy(at)squeakycode(dot)net>
Subject: Re: mysql to postgresql, performance questions
Date: 2010-03-22 01:14:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Note however that Oracle offeres full transactionality and does in place row
updates. There is more than one way to do it.


On Mar 21, 2010 5:43 PM, "Merlin Moncure" <mmoncure(at)gmail(dot)com> wrote:

On Sat, Mar 20, 2010 at 11:47 PM, Andy Colson <andy(at)squeakycode(dot)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


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

In response to


pgsql-performance by date

Next:From: Craig RingerDate: 2010-03-22 02:46:32
Subject: Re: GZIP of pre-zipped output
Previous:From: Merlin MoncureDate: 2010-03-21 22:43:06
Subject: Re: mysql to postgresql, performance questions

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