Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 97CA89FB28B for ; Mon, 16 Jul 2007 07:01:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 80783-08 for ; Mon, 16 Jul 2007 07:01:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id F17F09FA37A for ; Mon, 16 Jul 2007 07:01:25 -0300 (ADT) Received: from hawking.credativ.lan (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 4ECEC784BF for ; Mon, 16 Jul 2007 11:59:42 +0200 (CEST) From: Peter Eisentraut To: pgsql-docs@postgresql.org Subject: GNU tar and PITR Date: Mon, 16 Jul 2007 12:01:13 +0200 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200707161201.13302.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/5 X-Sequence-Number: 4332 http://developer.postgresql.org/pgdocs/postgres/continuous-archiving.html says: """ Also, some versions of GNU tar consider it an error if a file is changed while tar is copying it. There does not seem to be any very convenient way to distinguish this error from other types of errors, other than manual inspection of tar's messages. GNU tar is therefore not the best tool for making base backups. """ However, GNU tar returns 2 for a real error and 1 for the file changed case. Isn't that sufficient? -- Peter Eisentraut http://developer.postgresql.org/~petere/