Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 26EBC9FB251 for ; Sun, 13 May 2007 19:44:22 -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 03509-01-4 for ; Sun, 13 May 2007 19:44:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 31BF69FB341 for ; Sun, 13 May 2007 19:44:16 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 17A4556495; Sun, 13 May 2007 17:44:15 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Sun, 13 May 2007 17:44:09 -0500 Date: Sun, 13 May 2007 17:44:09 -0500 From: "Jim C. Nasby" To: Jeff Davis Cc: Dhaval Shah , pgsql-docs@postgresql.org Subject: Re: [GENERAL] PITR and tar Message-ID: <20070513224408.GC69517@nasby.net> References: <1178564286.23358.7.camel@dogma.v10.wvs> <1178644610.24902.20.camel@dogma.v10.wvs> <1178645330.24902.22.camel@dogma.v10.wvs> <565237760705090845j765e91bet522bb07cfb8995aa@mail.gmail.com> <1178731145.24902.70.camel@dogma.v10.wvs> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1178731145.24902.70.camel@dogma.v10.wvs> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070513:pgsql@j-davis.com::TnQhKe80lLimMn03:00000000000000000000 0000000000000000000000003piL X-Hashcash: 1:20:070513:dhaval.shah.m@gmail.com::bQkCWdHgSRKMMuJH:00000000000000 000000000000000000000000FV6V X-Hashcash: 1:20:070513:pgsql-docs@postgresql.org::pzFzKuX3ONrdBeDw:000000000000 0000000000000000000000003+pm X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/11 X-Sequence-Number: 4240 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. 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)