| From: | J Sisson <sisson(dot)j(at)gmail(dot)com> |
|---|---|
| To: | Rob Wultsch <wultsch(at)gmail(dot)com> |
| Cc: | "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 14:13:17 |
| Message-ID: | BANLkTikq_W=7M1Z-Kr1CyLgDkq8AgnBKXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
I'll concede that the issues we had with MySQL were self-inflicted for
using MyISAM. Thanks for pointing this out. Time to go get my
knowledge of MySQL up to par with my knowledge of PostgreSQL...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-04-26 14:58:49 | Re: Time to put theory to the test? |
| Previous Message | Sok Ann Yap | 2011-04-26 09:49:05 | reducing random_page_cost from 4 to 2 to force index scan |