From: Chander Ganesan <chander@otg-nc.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: Dominic Carlucci <carlucci@cae.com>
Cc: pgsql-general@postgresql.org
Cc: pgsql-admin@postgresql.org
Cc: carlucci@cae.ca
Subject: Re: [GENERAL] Backup
Date: Thu, 31 Jan 2008 10:00:28 -0500
Message-ID: <47A1E28C.8030708@otg-nc.com> (raw)
In-Reply-To: <1201786128.4453.287.camel@ebony.site>
References: <00a201c85ee9$fbd1ca00$9b0014ac@wbaus090>
<1201252875.4257.387.camel@ebony.site>
<47A1BD51.3030902@otg-nc.com>
<1201786128.4453.287.camel@ebony.site>
Simon Riggs wrote:
> On Thu, 2008-01-31 at 07:21 -0500, Chander Ganesan wrote:
>
>> If you don't mind if you lose some transactions
>>
>
> 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.
>
> As far as I am concerned, if any Postgres user loses data then we're all
> responsible.
>
I understand your point, but indicating that you can't trust a
point-in-time snapshot of the database is, IMHO, the same as saying you
can't trust PostgreSQL's automatic crash recovery, since the two are
essentially the same thing...
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com
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: chander@otg-nc.com, simon@2ndquadrant.com, phillip.smith@weatherbeeta.com.au, carlucci@cae.com, pgsql-admin@postgresql.org, carlucci@cae.ca
Subject: Re: [GENERAL] Backup
In-Reply-To: <47A1E28C.8030708@otg-nc.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