From: Magnus Hagander <magnus@hagander.net>
To: Simon Riggs <simon@2ndquadrant.com>
To: Chander Ganesan <chander@otg-nc.com>
To: Phillip Smith <phillip.smith@weatherbeeta.com.au>
To: Dominic Carlucci <carlucci@cae.com>
To: pgsql-general@postgresql.org
To: pgsql-admin@postgresql.org
To: carlucci@cae.ca
Subject: Re: [GENERAL] Backup
Date: Thu, 31 Jan 2008 15:43:14 +0100
Message-ID: <20080131144314.GH11977@svr2.hagander.net> (raw)
In-Reply-To: <20080131143405.GC21660@svana.org>
References: <00a201c85ee9$fbd1ca00$9b0014ac@wbaus090>
<1201252875.4257.387.camel@ebony.site>
<47A1BD51.3030902@otg-nc.com>
<1201786128.4453.287.camel@ebony.site>
<20080131143405.GC21660@svana.org>
On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
> On Thu, Jan 31, 2008 at 01:28:48PM +0000, Simon Riggs wrote:
> > That sentence has no place in any discussion about "backup" because the
> > risk is not just a few transactions, it is a corrupt and inconsistent
> > database from which both old and new data would be inaccessible.
>
> Hmm? I thought the whole point of a filesystem snapshot was that it's
> the same as if the system crashed. And I was fairly sure we could
> recover from that...
That was my assumption as well. *Assuming* that the filesystem snapshot is
consistent. There are a bunch of solutions that don't do consistent
snapshots between different partitions, so if your WAL or one tablespace is
on a different partition, you'll get corruption anyway... (seen this in
Big Commercial Database, so that's not a pg problem)
//Magnus
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-general@postgresql.org
Cc: magnus@hagander.net, simon@2ndquadrant.com, chander@otg-nc.com, phillip.smith@weatherbeeta.com.au, carlucci@cae.com, pgsql-admin@postgresql.org, carlucci@cae.ca
Subject: Re: [GENERAL] Backup
In-Reply-To: <20080131144314.GH11977@svr2.hagander.net>
* 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