Euler Taveira de Oliveira <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It seems to me that there basically is no graceful solution to this sort
>> of mismatch. It might be possible to kluge things so that we disable
>> NLS once we've recursed too many times in error processing, but that's
>> s
JiangWei <[EMAIL PROTECTED]> writes:
> LANG=zh_CN.UTF-8
> [ set client_encoding to LATIN1 and provoke an error ]
OK, I can reproduce the crash after initdb'ing with that LANG setting
(in an nls-enabled build). The postmaster log fills with a whole lot
of occurrences of
è¦å: 忽ç¥ä¸
* BUG #1:
=> SELECT '(100)':: t_1;
t_1
---
(100)
(1 row)
---
* BUG #2:
=> \encoding
UTF8
=> show server_e
=?UTF-8?Q?=E7=BB=B4_?= =?UTF-8?Q?=E5=A7=9C?= <[EMAIL PROTECTED]> writes:
> => \encoding ISO_8859_1
> => SELECT row(100):: t_1;
> server closed the connection unexpectedly
Works for me:
regression=# SELECT row(100):: t_1;
ERROR: value for domain d_1 violates check constraint "d_1_check"
regressio
# pg8.1.3
=> CREATE DOMAIN d_1 integer CHECK (VALUE < 10);
=> CREATE TYPE t_1 AS (m d_1);
=> SELECT '(100)':: t_1;
t_1
---
(100)
(1 row)
=> SELECT row(100):: t_1;
错误: 域 d_1 的值违反了检查约束 "d_1_check"
=> \encoding ISO_8859_1
=> SELECT row(100):: t_1;
server closed the connection unexpectedly
