Greg Smith wrote:
> 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.
A Perl script using the (standard) File::Copy module along with the
builtin function rename() should be moderately portable. It would to be
nice not to have to maintain two scripts.
In response to
pgsql-hackers by date
|Next:||From: Marko Kreen||Date: 2008-07-28 16:16:48|
|Subject: dblink security|
|Previous:||From: Andrew Dunstan||Date: 2008-07-28 16:01:40|
|Subject: Re: Do we really want to migrate plproxy and citext into
PG core distribution?|
pgsql-patches by date
|Next:||From: Gregory Stark||Date: 2008-07-28 16:33:29|
|Subject: Re: WITH RECUSIVE patches 0723|
|Previous:||From: Greg Smith||Date: 2008-07-28 15:59:12|
|Subject: Re: [PATCHES] odd output in restore mode|