Re: [PATCHES] odd output in restore mode - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [PATCHES] odd output in restore mode
Date
Msg-id 4891E2BC.203@enterprisedb.com
Whole thread Raw
In response to Re: [PATCHES] odd output in restore mode  (Martin Zaun <Martin.Zaun@Sun.COM>)
Responses Re: [PATCHES] odd output in restore mode  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Martin Zaun wrote:
> Heikki Linnakangas wrote:
>> Andrew Dunstan wrote:
>>> Greg Smith wrote:
>>>> On Wed, 23 Jul 2008, Kevin Grittner wrote:
>>>>
>>>> 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.
>>
>> It's also not very nice to require a Perl installation on Windows,
>> just for a replacement of Copy. Would a simple .bat script work?
>
> With these avenues to be explored, can the pg_standby patch on the
> CommitFest wiki be moved to the "Returned with Feedback" section?

Yes, I think we can conclude that we don't want this patch as it is.
Instead, we want a documentation patch that describes the problem,
mentioning that GNU cp is safe, or you can use the copy+rename trick.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Dumping datconfig
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] odd output in restore mode