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