From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: sisson.j@gmail.com
To: wultsch@gmail.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Time to put theory to the test?
Date: Tue, 26 Apr 2011 18:30:51 +1200
Message-ID: <4DB6669B.3090508@catalyst.net.nz> (raw)
In-Reply-To: <BANLkTikzg0JMtXPB0E=v_=GTPh2AoAf3oQ@mail.gmail.com>
References: <BANLkTi=17nkF9KiU24VFySbwLH_acKjBZQ@mail.gmail.com>
<BANLkTikzg0JMtXPB0E=v_=GTPh2AoAf3oQ@mail.gmail.com>
On 26/04/11 15:04, Rob Wultsch wrote:
> On Mon, Apr 25, 2011 at 12:30 PM, J Sisson<sisson.j@gmail.com> wrote:
>> machines, and virtually every MySQL machine has required data cleanup
>> and table scans and tweaks to get it back to "production" status.
> Tip from someone that manages thousands of MySQL servers: Use InnoDB
> when using MySQL. Using a crash unsafe product will yield undesirable
> results when a server crashes. It is also faster for many use cases.
>
> InnoDB is crash safe. It is just that simple.
>
+1
Or even switch to the Mariadb fork and use the crash safe Aria engine
[1] instead of Myisam if you must be without transactions. That has the
additional benefit of getting out from under the "Big O" - which is
always nice!
Cheers
Mark
[1] I have not personally tested that Aria is crash safe, but can attest
that Innodb certainly is.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mark.kirkwood@catalyst.net.nz, sisson.j@gmail.com, wultsch@gmail.com
Subject: Re: Time to put theory to the test?
In-Reply-To: <4DB6669B.3090508@catalyst.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox