From: Alan Hodgson <ahodgson@simkin.ca>
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
Message-ID: <200609181401.03679@hal.medialogik.com> (raw)
In-Reply-To: <b42b73150609181356r30453d46lf8b8171a613910d5@mail.gmail.com>
References: <C131DACC.31421%llonergan@greenplum.com>
<78ED28FACE63744386D68D8A9D1CF5D42099C7@MAIL.corp.lumeta.com>
<b42b73150609181356r30453d46lf8b8171a613910d5@mail.gmail.com>
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.
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: ahodgson@simkin.ca
Subject: Re: Large tables (was: RAID 0 not as fast as expected)
In-Reply-To: <200609181401.03679@hal.medialogik.com>
* 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