From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-admin@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Kenneth Marshall <ktm@rice.edu>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Subject: Re: tar, but not gnu tar
Date: Fri, 24 Aug 2007 13:59:43 +0200
Message-ID: <200708241359.44560.peter_e@gmx.net> (raw)
In-Reply-To: <16079.1187920691@sss.pgh.pa.us>
References: <200708231902.l7NJ2Ii28748@momjian.us>
<FE44E0D7EAD2ED4BB2165071DB8E328C03062B6D@egcrc-ex01.egcrc.org>
<16079.1187920691@sss.pgh.pa.us>
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.
"""
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
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: pgsql-admin@postgresql.org
Cc: peter_e@gmx.net, tgl@sss.pgh.pa.us, tsakai@gallo.ucsf.edu, bruce@momjian.us, ktm@rice.edu, Kevin.Grittner@wicourts.gov
Subject: Re: tar, but not gnu tar
In-Reply-To: <200708241359.44560.peter_e@gmx.net>
* 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