Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3C1879FBD4D for ; Tue, 8 May 2007 14:28:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 66783-02-9 for ; Tue, 8 May 2007 14:28:55 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from serv01.siteground137.com (ns1.siteground137.com [67.15.250.10]) by postgresql.org (Postfix) with ESMTP id 168CD9FBD2D for ; Tue, 8 May 2007 14:28:55 -0300 (ADT) Received: from nat.vinton.com ([209.162.219.253]:63527 helo=dogma.v10.wvs) by serv01.siteground137.com with esmtpa (Exim 4.52) id 1HlTUW-000534-Ip; Tue, 08 May 2007 12:28:48 -0500 Subject: Re: PITR and tar From: Jeff Davis To: Merlin Moncure Cc: Albe Laurenz , pgsql-general@postgresql.org In-Reply-To: References: <1178564286.23358.7.camel@dogma.v10.wvs> <1178644610.24902.20.camel@dogma.v10.wvs> Content-Type: text/plain Date: Tue, 08 May 2007 10:28:50 -0700 Message-Id: <1178645330.24902.22.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - serv01.siteground137.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - j-davis.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/376 X-Sequence-Number: 113571 On Tue, 2007-05-08 at 13:24 -0400, Merlin Moncure wrote: > On 5/8/07, Jeff Davis wrote: > > On Tue, 2007-05-08 at 08:47 +0200, Albe Laurenz wrote: > > > > The docs recommend using tar to perform a base backup for PITR. > > > > > > > > Usually, tar reports notices like: > > > > "tar: Truncated write; file may have grown while being archived." > > > > > > Did you call pg_start_backup(text) before you started to archive? > > > > > > > I was referring to the result of the tar itself being a corrupted gzip > > file (that couldn't be uncompressed with gunzip). > > > > I did indeed call pg_start/stop_backup(). > > is fsync on? > Yes. I have a battery-backed cache as well, and there were no power failures involved. Regards, Jeff Davis