Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 0B1859FA116 for ; Thu, 23 Aug 2007 01:23:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 64230-03 for ; Thu, 23 Aug 2007 01:23:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 2C9799FA16C for ; Thu, 23 Aug 2007 01:23:03 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l7N4MLk22375; Thu, 23 Aug 2007 00:22:21 -0400 (EDT) From: Bruce Momjian Message-Id: <200708230422.l7N4MLk22375@momjian.us> Subject: Re: tar, but not gnu tar In-Reply-To: To: Tena Sakai Date: Thu, 23 Aug 2007 00:22:21 -0400 (EDT) CC: Kenneth Marshall , Kevin Grittner , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/283 X-Sequence-Number: 26614 Tena Sakai wrote: > Hi Everybody, > > 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: > > There are many a ways to get the same thing done, but I > did it in a most intuitive way (to me). I had 3 windows > to the same directory. In one window, I ran a simple > shell program interactively and continuously: > while true > do > touch big.inputfile > done 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. -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +