Oh, yes, multiple quotes strings also cause problems :-(. You have no
idea how frustrating this was when I was writing initdb, and how hard it
was to find the problems.
The chdir solution might be best if we can do it, so that we only need
to quote the destination path.
cheers
andrew
markir@coretech.co.nz wrote:
>I tried out Andrew's suggestion, to no avail - none of the archive_commands
>below work:
>
>archive_command = 'copy "%p" "c:/databases/pgarchive/%f"'
>archive_command = 'copy \"%p\" \"c:/databases/pgarchive/%f\"'
>archive_command = 'copy \\"%p\\" \\"c:/databases/pgarchive/%f\\"' # desperation
>...
>
>A bit more investigation reveals that copy is bit selective about when it will
>accept quoted paths containing '/'.
>
>This works:
>
>cd c:\databases\pgdata\pg_xlog
>copy 00000001000000000000006A "c:/databases/pgarchive/00000001000000000000006A"
>
>This does not (unless your current directory is pg_xlog!):
>
>copy "c:/databases/pgdata/pg_xlog/00000001000000000000006A"
>"c:/databases/pgarchive/00000001000000000000006A"
>
>I guess this is not so bad if it is *just* 'copy' with this behaviour. I might
>try out winzip and see how I get on...
>
>regards (with some puzzlement)
>
>Mark
>
>
>Quoting Andrew Dunstan <andrew@dunslane.net>:
>
>
>
>>Not if you pass it to the Windows shell via system() or popen() - then
>>forward slashed paths need to be quoted. It's only the libraries that
>>understand forward slashes as God intended.
>>
>>
>
>
>
>
