Hi ITAGAKI-san.
I think that it is use restrictions now....This is not a BUG.
In Japan, use is restricted by the reason referred to as that server
encoding does not support all now. Then, It is Shift-jis encoding...
http://winpg.jp/~saito/pg_bug/copy_to.png
http://winpg.jp/~saito/pg_bug/copy_from.png
This SERVER_ENCODING is EUC_JP..:-(
This will be cleared by Shift_jis being supported as you suggested
before. Therefore, only psql to \copy of a client can do it now.
Probably, It will become the item of 'TODO' correctly.....
Is it different?
Or do you have another point?
Regards,
Hiroshi Saito
From: "ITAGAKI Takahiro"
The following bug has been logged online:
Bug reference: 3453
Logged by: ITAGAKI Takahiro
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2, 8.3dev
Operating system: independent (especially Windows)
Description: Error on COPY TO/FROM 'non-ascii-path'
Details:
When I set postgres a different character encoding from OS, COPY TO/FROM
'non-ascii-path' cannot open the path. The cause of the problem is that we
pass path-strings encoded in the server encoding to open() directly without
respect to the OS's native encodings.
It will be worse in Windows East Asia versions; Postgres doesn't support
their encodings as server encodings, so we cannot use non-ascii filenames
there.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
