Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 789619FB326 for ; Sun, 13 May 2007 22:05:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 33173-03 for ; Sun, 13 May 2007 22:04:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 3C67E9FB294 for ; Sun, 13 May 2007 22:04:57 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l4E14rn21632; Sun, 13 May 2007 21:04:53 -0400 (EDT) From: Bruce Momjian Message-Id: <200705140104.l4E14rn21632@momjian.us> Subject: Re: [GENERAL] PITR and tar In-Reply-To: <20070513224408.GC69517@nasby.net> To: "Jim C. Nasby" Date: Sun, 13 May 2007 21:04:53 -0400 (EDT) CC: Jeff Davis , Dhaval Shah , pgsql-docs@postgresql.org, Tom Lane 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: 200705/17 X-Sequence-Number: 4246 Jim C. Nasby wrote: > Moving to -docs... > > Does anyone know what the history of the docs saying that GNU tar had > issues with files changing underneath it? According to this report it's > actually BSD tar that has the issue. As I remember, Tom was the one who found that GNU tar would return a non-zero exit status if the file changed during backup, so you couldn't determine if the backup was successful based on the exit code. --------------------------------------------------------------------------- > > On Wed, May 09, 2007 at 10:19:05AM -0700, Jeff Davis wrote: > > On Wed, 2007-05-09 at 11:40 -0500, Jim Nasby wrote: > > > Actually, looking at the docs, the problem is with some versions of > > > GNU tar. AFAIK bsdtar is perfectly happy to archive files that have > > > changed from underneath it. > > > > > > > $ tar --version > > bsdtar 1.2.53 - libarchive 1.3.1 > > > > That fails to create a file in proper gzip format when the files are > > concurrently modified. > > > > However, > > > > $ tar --version > > tar (GNU tar) 1.14 > > Copyright (C) 2004 Free Software Foundation, Inc. > > This program comes with NO WARRANTY, to the extent permitted by law. > > You may redistribute it under the terms of the GNU General Public > > License; > > see the file named COPYING for details. > > Written by John Gilmore and Jay Fenlason. > > > > That _appears_ to work. > > > > Perhaps FreeBSD users should take notice of this problem. It's certainly > > not a postgresql problem, but I know there are a lot of freebsd users > > here, and using tar on fast-changing data may be rare outside of > > postgresql. > > > > Regards, > > Jeff Davis > > > > -- > Jim Nasby decibel@decibel.org > EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org/ -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +