Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 4CEBC6338A8 for ; Sun, 21 Mar 2010 19:43:18 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 48301-02 for ; Sun, 21 Mar 2010 22:43:01 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id A71DC6335FA for ; Sun, 21 Mar 2010 19:43:07 -0300 (ADT) Received: by vws6 with SMTP id 6so182858vws.19 for ; Sun, 21 Mar 2010 15:43:06 -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 :content-transfer-encoding; bh=kvNDv/d0IaXIYyJDrO5upGSxvhoIGql4pQriN4qMkMA=; b=w8RmZIVdGo9uZo3Xorr5ib0irOVA8dFSxO1TK4xIUNkcJLxtA8egdhqW+XvYqr3gcB u6KgS2y+TSEVf4NkSWld9GKcVDqPVuPDrTKJQXdcT/meh2qlKFsETkCw1AqmYqM7T/up rpR173trFLaj/083biNBI8QXYIuDlFv1Y84Lo= 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:content-transfer-encoding; b=btbW3fbz9b71infW0SgQOvWMlb3ZkaGLxOQjd+5L5dyHRuj4fo/OxO0qYuY7cCPvBw uK51LdP7Yo1dHR3YiGSiz1V2BZkBFKADfl8HZDy+kX1lCWcgK9XJompNXzDzVKsPGSbj 7B3120Ao0ri6gC7mtYj0LWKoF+NSr7fYh8TF0= MIME-Version: 1.0 Received: by 10.220.122.220 with SMTP id m28mr286049vcr.2.1269211386168; Sun, 21 Mar 2010 15:43:06 -0700 (PDT) In-Reply-To: <4BA596D2.4050406@squeakycode.net> References: <4BA23936.2030507@gmail.com> <4BA596D2.4050406@squeakycode.net> Date: Sun, 21 Mar 2010 18:43:06 -0400 Message-ID: Subject: Re: mysql to postgresql, performance questions From: Merlin Moncure To: Andy Colson Cc: Corin , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.516 tagged_above=-10 required=5 tests=AWL=0.083, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/262 X-Sequence-Number: 38087 On Sat, Mar 20, 2010 at 11:47 PM, Andy Colson wrote: > Don't underestimate mysql. =A0It was written to be fast. =A0But you have = to > understand the underling points: =A0It was written to be fast at the cost= of > other things... like concurrent access, and data integrity. =A0If you wan= t to > just read from a database, PG probably cant beat mysql. =A0But heres the > thing, your site does not just read. =A0Nor does it fire off the same sql= 10 > times. =A0So not a good test. 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