From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | psql & UTF8 |
Date: | 2005-12-09 10:39:50 |
Message-ID: | 43995EF6.60401@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Working on UTF support in tsearch2 I noticed different output of psql:
1) initdb with SQL_ASCII:
contrib_regression=# select 'jisa n asd n asld kl ans d
contrib_regression'# asdfjkl; asdf kl;amsdf';
?column?
-----------------------------------------------------------
jisa n asd n asld kl ans d
asdfjkl; asdf kl;amsdf
(1 row)
2) initdb with UTF8
contrib_regression=# select 'jisa n asd n asld kl ans d
contrib_regression'# asdfjkl; asdf kl;amsdf';
?column?
------------------------------------
jisa n asd n asld kl ans d
asdfjkl; asdf kl;amsdf
(1 row)
Length of '--------' string is different. This difference is a reason for
installcheck failture of tsearch2 on UTF8 inited db.
Is it supposed behaviour of psql?
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-12-09 10:59:12 | Re: Warm-cache prefetching |
Previous Message | David Fetter | 2005-12-09 09:10:00 | psql patch: new host/port |