Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3CAA49FC06D for ; Wed, 9 May 2007 14:19:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 29296-05 for ; Wed, 9 May 2007 14:19:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from serv01.siteground137.com (ns1.siteground137.com [67.15.250.10]) by postgresql.org (Postfix) with ESMTP id 71B159FB83A for ; Wed, 9 May 2007 14:19:10 -0300 (ADT) Received: from nat.vinton.com ([209.162.219.253]:58153 helo=dogma.v10.wvs) by serv01.siteground137.com with esmtpa (Exim 4.52) id 1Hlpoe-0005oD-53; Wed, 09 May 2007 12:19:04 -0500 Subject: Re: PITR and tar From: Jeff Davis To: Jim Nasby Cc: Dhaval Shah , pgsql-general@postgresql.org In-Reply-To: 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> Content-Type: text/plain Date: Wed, 09 May 2007 10:19:05 -0700 Message-Id: <1178731145.24902.70.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - serv01.siteground137.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - j-davis.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/464 X-Sequence-Number: 113659 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