Re: PITR on Win32 - Archive and Restore

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Christian Klemke <Christian(dot)Klemke(at)t-online(dot)de>
Cc: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, markir(at)coretech(dot)co(dot)nz, pgsql-hackers-win32 <pgsql-hackers-win32(at)postgresql(dot)org>, pgadmin(at)pse-consulting(dot)de, dpage(at)vale-housing(dot)co(dot)uk
Subject: Re: PITR on Win32 - Archive and Restore
Date: 2004-08-09 13:40:47
Message-ID: 41177EDF.8020003@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32


Christian,

what you have not done is to follow the context of the discussion. This
command is a configuration option, and thus executed with a system()
call. We do not have the luxury of hardcoding it available to us.

Note that system() actually calls cmd.exe, so your previous comment
about needing to use cmd /c is also wrong.

cheers

andrew

Christian Klemke wrote:

>Guys,
>
>did you notice my earlier CopyFile / CopyFileEx posting (at about 10:20
>German time) ?
>If you want to stick with an external copy executable (which I don't quite
>understand), just go and write one yourself and provide it for Windows
>users. Leaving aside the neccessary checks, it might be as simple as:
>
>#include <windows.h>
>int main(char* args[]) {
> return CopyFile(args[0],args[1],TRUE);
>}
>
>Adding a proprietary parser for secure handling of quotes (to deal of paths
>containing space)s should be simple, I'm sure you have adequate functions in
>your Postgres library. Link it to a file called copy.exe or cp.exe or
>wahtever and add it to the PGBIN directory.
>
>
>
>
>

In response to

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Andrew Dunstan 2004-08-09 13:58:20 Re: PITR on Win32 - Archive and Restore
Previous Message Merlin Moncure 2004-08-09 13:35:01 Re: PITR on Win32 - Archive and Restore