BUG #1456: COPY FROM error

Started by Pascal Van Puymbroeckabout 21 years ago2 messagesbugs
Jump to latest
#1Pascal Van Puymbroeck
pascal.vanpuymbroeck@zenonproductions.be

The following bug has been logged online:

Bug reference: 1456
Logged by: Pascal Van Puymbroeck
Email address: pascal.vanpuymbroeck@zenonproductions.be
PostgreSQL version: 8.0.1
Operating system: Windows 2000
Description: COPY FROM error
Details:

The COPY table FROM command works fine as long as you use drives local to
the machine like c: or e: , but when you try to use the command with a
network drive mapped to o: for eaxmple, you get a 'could not open file for
reading: invalid argument' error.

#2Magnus Hagander
magnus@hagander.net
In reply to: Pascal Van Puymbroeck (#1)
Re: BUG #1456: COPY FROM error

The following bug has been logged online:

Bug reference: 1456
Logged by: Pascal Van Puymbroeck
Email address: pascal.vanpuymbroeck@zenonproductions.be
PostgreSQL version: 8.0.1
Operating system: Windows 2000
Description: COPY FROM error
Details:

The COPY table FROM command works fine as long as you use
drives local to the machine like c: or e: , but when you try
to use the command with a network drive mapped to o: for
eaxmple, you get a 'could not open file for
reading: invalid argument' error.

This is to be expected - the server runs with it's own user account, and
as such it won't have access to your profile with it's mapped drives.
Your solutions are:

*) Use an UNC mapped path (\\server\share\dir\file). This will require
either postgresql running as a domain account, or anonymous SMB (which
you *really* should have turned off)

*) use psql's \copy command. This one will write the file from the
client, and using your own windows account, so it shuold work fine with
mapped drives. This is what I'd recommend if you're doing one-off loads,
but it might be a bit trickier if you want it integrated in an app.

//Magnus