Re: Time to put theory to the test?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: J Sisson <sisson(dot)j(at)gmail(dot)com>
Cc: Rob Wultsch <wultsch(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Time to put theory to the test?
Date: 2011-04-26 15:02:08
Message-ID: BANLkTik7S9Ov3cxYb6zOZLkn8pGvMxz-1g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Apr 26, 2011 at 8:13 AM, J Sisson <sisson(dot)j(at)gmail(dot)com> wrote:
> On Mon, Apr 25, 2011 at 10:04 PM, Rob Wultsch <wultsch(at)gmail(dot)com> wrote:
>> Tip from someone that manages thousands of MySQL servers: Use InnoDB
>> when using MySQL.
>
> Granted, my knowledge of PostgreSQL (and even MSSQL) far surpasses my
> knowledge of MySQL, but if InnoDB has such amazing benefits as being
> crash safe, and even speed increases in some instances, why isn't
> InnoDB default?  I suppose the real issue is that I prefer software
> that gives me safe defaults that I can adjust towards the "unsafe" end
> as far as I'm comfortable with, rather than starting off in la-la land
> and working back towards sanity.

Because for many read heavy workloads myisam is still faster. Note
that even if you use innodb tables, your system catalogs are stored in
myisam. The Drizzle project aims to fix such things, but I'd assume
they're a little ways from full production ready status.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Joel Reymont 2011-04-26 15:15:42 tuning on ec2
Previous Message Kevin Grittner 2011-04-26 14:58:49 Re: Time to put theory to the test?