pg.ddx.io  pgsql-patches@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Dave Page <dpage@pgadmin.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: List pgsql-patches <pgsql-patches@postgresql.org>
Cc: Martin Zaun <Martin.Zaun@Sun.COM>
Subject: Re: [PATCHES] odd output in restore mode
Date: Mon, 28 Jul 2008 11:59:12 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0807281136140.26479@westnet.com> (raw)
In-Reply-To: <48873C7E.EE98.0025.0@wicourts.gov>
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>

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



view thread (59+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0807281136140.26479@westnet.com>
Permalink:  ../Pine.GSO.4.64.0807281136140.26479@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0807281136140.26479@westnet.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-patches@postgresql.org
  Cc: gsmith@gregsmith.com, Kevin.Grittner@wicourts.gov, simon@2ndquadrant.com, heikki@enterprisedb.com, andrew@dunslane.net, bruce@momjian.us, dpage@pgadmin.org, pgsql-hackers@postgresql.org, Martin.Zaun@Sun.COM
  Subject: Re: [PATCHES] odd output in restore mode
  In-Reply-To: <Pine.GSO.4.64.0807281136140.26479@westnet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox