From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: PITR on Win32 - Archive and Restore |
Date: | 2004-08-10 18:23:48 |
Message-ID: | 4938.24.211.141.25.1092162228.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 pgsql-patches |
Tom Lane said:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> I have gotten confused by this. Does COPY work with quoted paths only
>> if we use forward slashes, or was this fix just for the slash issue
>> and not spaces?
>
> This only fixes the slash issue. If your database path includes spaces
> you'll still need to put quotes in the archive_command, but it
> shouldn't be any worse than
> archive_command = 'copy "%p" "c:\someplace\%f"'
>
> I'd appreciate confirmation though from some win32 users that the above
> indeed works.
>
That's what my experimentation showed, although I worked with a tiny test.c
file rather than the archive command. I think this is the right solution -
the user should put the quotes in, not postgres.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2004-08-10 20:40:40 | Re: pg_autovacuum Win32 Service Code |
Previous Message | Tom Lane | 2004-08-10 18:21:08 | Re: PITR on Win32 - Archive and Restore |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-08-10 18:32:55 | Re: pg_dump-zh_TW.po for current |
Previous Message | Tom Lane | 2004-08-10 18:21:08 | Re: PITR on Win32 - Archive and Restore |