Re: tar, but not gnu tar

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Kenneth Marshall" <ktm(at)rice(dot)edu>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: tar, but not gnu tar
Date: 2007-08-24 11:59:43
Message-ID: 200708241359.44560.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Am Freitag, 24. August 2007 03:58 schrieb Tom Lane:
> "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)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(at)rh2 ~]$ tar --version
> tar (GNU tar) 1.15.1
> [tgl(at)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(at)rh2 ~]$ echo $?
> 0
> [tgl(at)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/

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Shane Ambler 2007-08-24 12:42:38 Re: Possibilities of PgSQL
Previous Message Karel Břinda 2007-08-24 08:12:29 Re: Possibilities of PgSQL