diff options
| author | Bruce Momjian <bruce@momjian.us> | 2006-12-04 22:24:04 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2006-12-04 22:24:04 +0000 |
| commit | e1bfa1869f10f2445747239feb21882e8b56e0f1 (patch) | |
| tree | c02103456bfa7d2f7ba9ae0ea7079eaedc1a3721 /src/backend/commands/functioncmds.c | |
| parent | e72ef41d72d7555a574ff2197498f66b588bd24f (diff) | |
| download | postgresql-e1bfa1869f10f2445747239feb21882e8b56e0f1.tar.gz postgresql-e1bfa1869f10f2445747239feb21882e8b56e0f1.zip | |
Patch of Win32 Encoding problem for server messages using
FormatMessage() (This should have been in 8.2.0, patched to 8.2.X and
HEAD):
I think this problem to be complex....
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00042.php
FormatMessage of windows cannot consider the encoding of the database.
However, I should try the solution now. It is necessary to clear the
problem.
Multi character-code exists together in message and log. It doesn't
consider
the data base encoding that the user intended....
The user in multi-byte country can try this.
http://inet.winpg.jp/~saito/pg_bug/MessageCheck.c
That is, it is likely to become it in this manner.(Japanese)
http://inet.winpg.jp/~saito/pg_bug/FormatMessage998.png
Hiroshi Saito
Diffstat (limited to 'src/backend/commands/functioncmds.c')
0 files changed, 0 insertions, 0 deletions