Bruce Momjian writes:
> Has this been fixed already?
No. My suggestion of using bind_textdomain_codeset() might fix it,
but I'm not sufficiently familiar with the NLS code to want to try to
install that myself.
regards, tom lane
---(end of broadc
Has this been fixed already?
---
Qingqing Zhou wrote:
>
> My theory is "select;" incurs a parse error and this error message is
> supposed to be translated into your encoding, but unfortunately not every
> UTF8 character is
My theory is "select;" incurs a parse error and this error message is
supposed to be translated into your encoding, but unfortunately not every
UTF8 character is necessarily be encoded as GB18030, which will cause an
infinite recursive elogs just like this:
1:elog(parse_error)// contain u
Encoding in UTF-8
Bug:
C:\PostgreSQL>ver
Microsoft Windows [版本 5.2.3790]
C:\PostgreSQL>mkdir data
C:\PostgreSQL>bin\initdb -D data
C:\PostgreSQL>bin\postmaster -D data
C:\PostgreSQL\bin>psql -d template1
template1=# select version();
PostgreSQL 8.0.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC
