Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3D5F6650474; Mon, 28 Jul 2008 13:12:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 72242-09; Mon, 28 Jul 2008 13:12:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from westnet.com (westnet.com [216.187.52.2]) by postgresql.org (Postfix) with ESMTP id 3A0386502CA; Mon, 28 Jul 2008 12:59:41 -0300 (ADT) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id m6SFxEqY011125; Mon, 28 Jul 2008 11:59:14 -0400 (EDT) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id m6SFxCZ5011113; Mon, 28 Jul 2008 11:59:12 -0400 (EDT) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Mon, 28 Jul 2008 11:59:12 -0400 (EDT) From: Greg Smith X-X-Sender: gsmith@westnet.com To: Kevin Grittner cc: Simon Riggs , Heikki Linnakangas , Andrew Dunstan , Bruce Momjian , Dave Page , PostgreSQL-development , List pgsql-patches , Martin Zaun Subject: Re: [PATCHES] odd output in restore mode In-Reply-To: <48873C7E.EE98.0025.0@wicourts.gov> Message-ID: References: <200807011520.m61FKhZ20311@momjian.us> <48867904.9090001@sun.com> <1216810783.3894.602.camel@ebony.2ndQuadrant> <48877AC0.7070603@enterprisedb.com> <48873C7E.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/1300 X-Sequence-Number: 121560 On Wed, 23 Jul 2008, Kevin Grittner wrote: > In our scripts we handle this by copying to a temp directory on the > same mount point as the archive directory and doing a mv to the > archive location when the copy is successfully completed. I think > that this even works on Windows. Could that just be documented as a > strong recommendation for the archive script? This is exactly what I always do. I think the way cp is shown in the examples promotes what's really a bad practice for lots of reasons, this particular problem being just one of them. I've been working on an improved archive_command shell script that I expect to submit for comments and potential inclusion in the documentation as a better base for other people to build on. This is one of the options for how it can operate. It would be painful but not impossible to convert a subset of that script to run under Windows as well, at least enough to cover this particular issue. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD