X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 546AE9DC9F7;
	Tue, 27 Dec 2005 15:56:51 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 76414-10; Tue, 27 Dec 2005 15:56:48 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from trolak.mydnsbox2.com (ns1.mydnsbox2.com [207.44.142.118])
	by postgresql.org (Postfix) with ESMTP id C22879DC815;
	Tue, 27 Dec 2005 15:56:45 -0400 (AST)
Received: from dunslane.net (localhost.localdomain [127.0.0.1])
	(authenticated (0 bits))
	by trolak.mydnsbox2.com (8.11.6/8.11.6) with ESMTP id jBRKEtB02593;
	Tue, 27 Dec 2005 14:14:55 -0600
Received: from 68.143.134.146
	(SquirrelMail authenticated user andrew@dunslane.net)
	by www.dunslane.net with HTTP; Tue, 27 Dec 2005 14:14:55 -0600 (CST)
Message-ID: <41278.68.143.134.146.1135714495.squirrel@www.dunslane.net>
Date: Tue, 27 Dec 2005 14:14:55 -0600 (CST)
Subject: Re: [HACKERS] Online backup vs Continuous backup
From: "Andrew Dunstan" <andrew@dunslane.net>
To: <gsstark@mit.edu>
In-Reply-To: <87mzim5psy.fsf@stark.xeocode.com>
References: <87mzim5psy.fsf@stark.xeocode.com>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Cc: <pgman@candle.pha.pa.us>, <pgsql-hackers@postgresql.org>,
	<pgsql-docs@postgresql.org>
X-Mailer: SquirrelMail (version 1.2.5)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.06 required=5 tests=[AWL=0.060]
X-Spam-Score: 0.06
X-Spam-Level: 
X-Archive-Number: 200512/36
X-Sequence-Number: 3384

Greg Stark said:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>
>> I noticed that we are using the term "Online Backup" in our
>> documentation when we are talking about continuous backup and PITR.
>>
>> To me, "online backup" is doing a backup while the system is online
>> (online-backup), and that is accomplished by pg_dump.
>
> Well fwiw what pg_dump does isn't even considered a "backup" at all in
> other systems. It's a "logical export" or something of that sort.
>
> It's not considered a "backup" because it's saving something different
> than the actual physical database. When you restore you get something
> (hopefully) logically equivalent but still physically different.


This seems fairly arbitrary. On that basis anything on a higher level than
dd is not a backup method, ISTM.

cheers

andrew