X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id AE6CC9FA383
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 18 Sep 2006 18:02:04 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 38185-03 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 18 Sep 2006 21:01:07 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from skynet.simkin.ca (skynet.simkin.ca [199.175.137.210])
	by postgresql.org (Postfix) with ESMTP id 756549FA3A0
	for <pgsql-performance@postgresql.org>;
	Mon, 18 Sep 2006 18:01:07 -0300 (ADT)
Received: from hal.simkin.ca (S0106000c6eb33e73.vc.shawcable.net
	[24.80.109.220])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by skynet.simkin.ca (Postfix) with ESMTP id AAC85FAF4
	for <pgsql-performance@postgresql.org>;
	Mon, 18 Sep 2006 14:01:05 -0700 (PDT)
From: Alan Hodgson <ahodgson@simkin.ca>
Organization: Simkin Network Consulting
To: pgsql-performance@postgresql.org
Subject: Re: Large tables (was: RAID 0 not as fast as expected)
Date: Mon, 18 Sep 2006 14:01:03 -0700
User-Agent: KMail/1.9.1
References: <C131DACC.31421%llonergan@greenplum.com>
	<78ED28FACE63744386D68D8A9D1CF5D42099C7@MAIL.corp.lumeta.com>
	<b42b73150609181356r30453d46lf8b8171a613910d5@mail.gmail.com>
In-Reply-To: <b42b73150609181356r30453d46lf8b8171a613910d5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200609181401.03679@hal.medialogik.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.133 tagged_above=0 required=5
	tests=FORGED_RCVD_HELO, SPF_HELO_PASS, SPF_PASS
X-Spam-Level: 
X-Archive-Number: 200609/233
X-Sequence-Number: 20919

On Monday 18 September 2006 13:56, "Merlin Moncure" <mmoncure@gmail.com> 
wrote:
> just another fyi, if you have a really big database, you can forget
> about doing pg_dump for backups (unless you really don't care about
> being x day or days behind)...you simply have to due some type of
> replication/failover strategy.  i would start with pitr.

And, of course, the biggest problem of all; upgrades.

-- 
Eat right. Exercise regularly. Die anyway.