From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: Kenneth Marshall <ktm@rice.edu>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: tar, but not gnu tar
Date: Thu, 23 Aug 2007 01:18:24 -0400
Message-ID: <17438.1187846304@sss.pgh.pa.us> (raw)
In-Reply-To: <200708230422.l7N4MLk22375@momjian.us>
References: <200708230422.l7N4MLk22375@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> Tena Sakai wrote:
>> I had a bit of time to experiment with tar and star today
>> and I am no longer sure what the real issue is. Perhaps
>> some of you can clarify. Here's the test I ran:
> I don't think 'touch' is enough for tar to see the file as changed (you
> are only updating metadata). (tar did complain but the file contents
> didn't so it is hard to say if that is a good test.) You should change
> the file contents during the backup.
In fact, I'll bet that you have to change the file *length* during the
backup to trigger gnu tar's complaint. If it were rigorously checking
for file content change, it'd have to read the whole of every file
twice, which hardly seems like overhead that anyone would accept. But a
check for length change would just mean one extra stat() call per file,
which is a whole lot more plausible.
regards, tom lane
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: tgl@sss.pgh.pa.us, bruce@momjian.us, tsakai@gallo.ucsf.edu, ktm@rice.edu, Kevin.Grittner@wicourts.gov
Subject: Re: tar, but not gnu tar
In-Reply-To: <17438.1187846304@sss.pgh.pa.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