From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-admin@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: Kenneth Marshall <ktm@rice.edu>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Subject: Re: tar, but not gnu tar
Date: Fri, 14 Sep 2007 00:16:14 -0400 (EDT)
Message-ID: <200709140416.l8E4GEM28623@momjian.us> (raw)
In-Reply-To: <200708241359.44560.peter_e@gmx.net>
Peter Eisentraut wrote:
> Am Freitag, 24. August 2007 03:58 schrieb Tom Lane:
> > "Tena Sakai" <tsakai@gallo.ucsf.edu> writes:
> > >> This seems to contradict what we say about GNU tar?
> > >> Is this GNU tar? What version?
> > >
> > > Yes, it is GNU tar v1.14
> >
> > FWIW, I tried this on Fedora Core 6 while running pgbench:
> >
> > [tgl@rh2 ~]$ tar --version
> > tar (GNU tar) 1.15.1
> > [tgl@rh2 ~]$ tar cf t.tar $PGDATA
> > tar: Removing leading `/' from member names
> > tar: /home/tgl/testversion/data/pg_xlog/000000010000000000000003: file
> > changed as we read it [tgl@rh2 ~]$ echo $?
> > 0
> > [tgl@rh2 ~]$
> >
> > ISTR that the original caution was against writing scripts that assume
> > anything being emitted to stderr must indicate a problem.
>
> The relevant NEWS entry from GNU tar 1.16 is:
>
> """
> * After creating an archive, tar exits with code 1 if some files were
> changed while being read. Previous versions exited with code 2 (fatal
> error), and only if some files were truncated while being archived.
Docs updated and backpatched to 8.2.X:
Also, some versions of GNU <application>tar</> consider it an error
if a file was truncated while <application>tar</> is copying it.
Fortunately, GNU <application>tar</> versions 1.16 and later exits
with <literal>1</> if a file was changed during the backup, and
<literal>2</> for other errors.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bruce@momjian.us, peter_e@gmx.net, tgl@sss.pgh.pa.us, tsakai@gallo.ucsf.edu, ktm@rice.edu, Kevin.Grittner@wicourts.gov
Subject: Re: tar, but not gnu tar
In-Reply-To: <200709140416.l8E4GEM28623@momjian.us>
References: <200708241359.44560.peter_e@gmx.net> <200709140416.l8E4GEM28623@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox