| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Chander Ganesan <chander(at)otg-nc(dot)com>, Phillip Smith <phillip(dot)smith(at)weatherbeeta(dot)com(dot)au>, 'Dominic Carlucci' <carlucci(at)cae(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org, carlucci(at)cae(dot)ca |
| Subject: | Re: [GENERAL] Backup |
| Date: | 2008-01-31 14:43:14 |
| Message-ID: | 20080131144314.GH11977@svr2.hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chander Ganesan | 2008-01-31 15:00:28 | Re: [GENERAL] Backup |
| Previous Message | Martijn van Oosterhout | 2008-01-31 14:34:05 | Re: [GENERAL] Backup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Douglas McNaught | 2008-01-31 14:53:18 | Re: Log file permissions? |
| Previous Message | Martijn van Oosterhout | 2008-01-31 14:34:05 | Re: [GENERAL] Backup |