Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BB74B9FBCF0 for ; Wed, 9 May 2007 13:41:04 -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 72160-05 for ; Wed, 9 May 2007 13:40:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 3CA939FB596 for ; Wed, 9 May 2007 13:40:58 -0300 (ADT) Received: from [10.82.1.66] (docboy.decibel.org [65.86.67.34]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id 0411F56448; Wed, 9 May 2007 11:40:55 -0500 (CDT) In-Reply-To: <565237760705090845j765e91bet522bb07cfb8995aa@mail.gmail.com> References: <1178564286.23358.7.camel@dogma.v10.wvs> <1178644610.24902.20.camel@dogma.v10.wvs> <1178645330.24902.22.camel@dogma.v10.wvs> <565237760705090845j765e91bet522bb07cfb8995aa@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: "Jeff Davis" , pgsql-general@postgresql.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: PITR and tar Date: Wed, 9 May 2007 11:40:57 -0500 To: Dhaval Shah X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/461 X-Sequence-Number: 113656 Actually, looking at the docs, the problem is with some versions of GNU tar. AFAIK bsdtar is perfectly happy to archive files that have changed from underneath it. On May 9, 2007, at 10:45 AM, Dhaval Shah wrote: > Looks like a problem specific to FreeBSD. I use Centos/postgres 8.2.3 > and I do not see that problem at all. > > Dhaval > > On 5/8/07, Jeff Davis wrote: >> 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 >> >> >> ---------------------------(end of >> broadcast)--------------------------- >> TIP 3: Have you checked our extensive FAQ? >> >> http://www.postgresql.org/docs/faq >> > > > -- > Dhaval Shah > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)