Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 7CBE41337999
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 26 Apr 2011 03:31:20 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 77905-09
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 26 Apr 2011 06:30:58 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.catalyst.net.nz (bertrand.catalyst.net.nz [202.78.240.40])
	by mail.postgresql.org (Postfix) with ESMTP id BDE61133740B
	for <pgsql-performance@postgresql.org>;
	Tue, 26 Apr 2011 03:30:57 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by mail.catalyst.net.nz (Postfix) with ESMTP id E0C0431FBE;
	Tue, 26 Apr 2011 18:30:53 +1200 (NZST)
X-Virus-Scanned: Debian amavisd-new at catalyst.net.nz
Received: from mail.catalyst.net.nz ([127.0.0.1])
	by localhost (bertrand.catalyst.net.nz [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id ISKQ-4KvkjCC; Tue, 26 Apr 2011 18:30:53 +1200 (NZST)
Received: from [192.168.1.11] (122-60-64-230.jetstream.xtra.co.nz
	[122.60.64.230]) (Authenticated sender: mark.kirkwood)
	by mail.catalyst.net.nz (Postfix) with ESMTPSA id DC84431F67;
	Tue, 26 Apr 2011 18:30:52 +1200 (NZST)
Message-ID: <4DB6669B.3090508@catalyst.net.nz>
Date: Tue, 26 Apr 2011 18:30:51 +1200
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: sisson.j@gmail.com, wultsch@gmail.com
CC: pgsql-performance@postgresql.org
Subject: Re: Time to put theory to the test?
References: <BANLkTi=17nkF9KiU24VFySbwLH_acKjBZQ@mail.gmail.com>
	<BANLkTikzg0JMtXPB0E=v_=GTPh2AoAf3oQ@mail.gmail.com>
In-Reply-To: <BANLkTikzg0JMtXPB0E=v_=GTPh2AoAf3oQ@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------060508080005020807060309"
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.909 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201104/350
X-Sequence-Number: 43412

This is a multi-part message in MIME format.
--------------060508080005020807060309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.

--------------060508080005020807060309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    On 26/04/11 15:04, Rob Wultsch wrote:
    <blockquote
      cite="mid:BANLkTikzg0JMtXPB0E=v_=GTPh2AoAf3oQ@mail.gmail.com"
      type="cite">
      <pre wrap="">On Mon, Apr 25, 2011 at 12:30 PM, J Sisson <a class="moz-txt-link-rfc2396E" href="mailto:sisson.j@gmail.com">&lt;sisson.j@gmail.com&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">machines, and virtually every MySQL machine has required data cleanup
and table scans and tweaks to get it back to "production" status.
</pre>
      </blockquote>
      <pre wrap="">
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.

</pre>
    </blockquote>
    <font size="-1"><font face="Helvetica">+1<br>
        <br>
        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!<br>
        <br>
        Cheers<br>
        <br>
        Mark<br>
        <br>
        [1] I have not personally tested that Aria is crash safe, but
        can attest that Innodb certainly is.<br>
      </font></font>
  </body>
</html>

--------------060508080005020807060309--