The following bug has been logged online:

Bug reference: 1819
Logged by: Steve Peterson
Email address: steve (AT) zpfe (DOT) com
PostgreSQL version: 8.0.3
Operating system: Windows XP SP 2
Description: COPY filename rejects Windows format path
Details:

Running COPY FROM on a Windows server; using a Windows-format fully
qualified path with backslashes results in the backslashes being interpreted
as escapes.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Steve Peterson wrote:
Did you escape the backslashes: C:\\Windows\\Path ?

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Steve Peterson wrote:

Windows APIs are perfectly happy with regular / forward slashes in pathnames,
in fact, I use them everywhere BUT in command line interfaces.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

At 09:47 AM 8/11/2005, Richard Huxton wrote:
Nope. I used a standard Windows path, copied from the address field in
Windows explorer.

I see now on
http://www.postgresql.org/docs/8.0/i...NTAX-CONSTANTS
(I know, RTFM) that it's documented that the SQL string literal is extended
to accept backslash as an escape, so this is a documented behavior. Can I
convert this bug into a docs bug -- to mention the escaping process
wherever a filename is specified in a SQL string constant?

S


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster