diff options
| author | Bruce Momjian <bruce@momjian.us> | 2006-12-04 22:23:40 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2006-12-04 22:23:40 +0000 |
| commit | 1e22e605050eded6ed49f049678782dba9e864cf (patch) | |
| tree | d4081c43de8e4bb2eb0a519a56a6c76c29f661cf /src/backend/utils/adt/pgstatfuncs.c | |
| parent | 6cd9a58480e37e11adf7fa7d406ba118d2a7e4e5 (diff) | |
| download | postgresql-1e22e605050eded6ed49f049678782dba9e864cf.tar.gz postgresql-1e22e605050eded6ed49f049678782dba9e864cf.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/utils/adt/pgstatfuncs.c')
0 files changed, 0 insertions, 0 deletions