| From: | "patrick" <patrick(at)11h11(dot)com> |
|---|---|
| To: | "Richard Huxton" <dev(at)archonet(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |
| Date: | 2008-03-19 20:11:22 |
| Message-ID: | 00f001c889fd$69406c20$0d02a8c0@audio |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
SELECT 'abc'::text || 'def'::text;
it's working fine (no need to convert the query ASCII to UTF8 or such
i am using pgadmin (1.8.2) to pass the query:
show client_encoding = UNICODE.
in postgresql.conf i have:
client_encoding; Value = UTF8, Current value = UNICODE;
i tried to restart postgresql for reloading his configuration, but it's
still UNICODE...
reinstalling postgresql 8.3.1 on windows and leaving the server encoding and
client encoding to default (cannot remember what was it - something like
WIN1252 or such) then i have no more problem, but i am worry about the
impact of transfering the database to linux (eventually i would like to
transfer my database to my linux server)...
pat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keaton Adams | 2008-03-19 20:28:33 | How to concatenate a boolean to a text string for an EXECUTE stmt in a stored proc |
| Previous Message | Tom Lane | 2008-03-19 19:44:30 | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Denne | 2008-03-19 21:54:31 | Re: count(*) performance improvement ideas |
| Previous Message | Tom Lane | 2008-03-19 19:44:30 | Re: tsearch2 in postgresql 8.3.1 - invalid byte sequence for encoding "UTF8": 0xc3 |