public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim Nasby <[email protected]>
To: Dhaval Shah <[email protected]>
Cc: Jeff Davis <[email protected]>
Cc: [email protected]
Subject: Re: PITR and tar
Date: Wed, 9 May 2007 11:40:57 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<AFCCBB403D7E7A4581E48F20AF3E5DB20291A531@EXADV1.host.magwien.gv.at>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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 <[email protected]> wrote:
>> On Tue, 2007-05-08 at 13:24 -0400, Merlin Moncure wrote:
>> > On 5/8/07, Jeff Davis <[email protected]> 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                                            [email protected]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

view thread (13+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PITR and tar
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox