Skip site navigation (1) Skip section navigation (2)

Re: Solution of the file name problem of copy on windows.

From: Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Solution of the file name problem of copy on windows.
Date: 2009-04-13 10:13:15
Message-ID: 20090413184335.39BE.52131E4D@oss.ntt.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:

> "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> wrote:
> 
> > Um,  I had a focus in help the problem which is not avoided. 
> > I am not sensitive to a problem being avoided depending on usage. 
> > However, I will wish to work spontaneously, when it is help much. 
> 
> I'll research whether encoding of filesystem path is affected by
> locale settings or not in some platforms. Also, we need to research
> where we should get the system encoding when the locale is set to "C",
> which is popular in Japanese users.

Here is a patch to implement GetPlatformEncoding() and convert absolute
file paths from database encoding to platform encoding. Since encoding
of paths are converted at AllocateFile() and BasicOpenFile(), not only
COPY TO/FROM but also almost of file operations are covered by the patch.
Callers of file access methods don't have to modify their codes.

Please test the patch in a variety of platforms. I tested it on Windows
and Linux, and then I found {PG_UTF8, "ANSI_X3.4-1968"} is required for
encoding_match_list in src/port/chklocale.c on Linux (FC6).

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center


Attachment: GetPlatformEncoding.patch
Description: application/octet-stream (6.3 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Guillaume SmetDate: 2009-04-13 10:21:41
Subject: Re: New trigger option of pg_standby
Previous:From: Fujii MasaoDate: 2009-04-13 05:52:29
Subject: Re: New trigger option of pg_standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group