Re: Determining client_encoding from client locale
Jaime Casanova <jcasanov@systemguards.com.ec>
From: Jaime Casanova <jcasanov@systemguards.com.ec>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>, pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>, Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>, Peter Eisentraut <peter_e@gmx.net>
Date: 2009-08-24T19:09:40Z
Lists: pgsql-hackers
Attachments
- client_encoding_test_linux.txt (text/plain)
- client_encoding_test_win.txt (text/plain)
On Wed, Aug 19, 2009 at 11:08 AM, Jaime Casanova<jcasanov@systemguards.com.ec> wrote: > On Tue, Aug 18, 2009 at 6:49 AM, Heikki > Linnakangas<heikki.linnakangas@enterprisedb.com> wrote: >> >> Hmm, are you sure you the right version of libpq is being loaded at >> runtime? What does "ldd ./test-libpq" say? >> > attached the results of ldd and the result of the test script for "client_encoding=auto" and "client_encoding=latin1", seems like it's trying to use auto as an encoding and when it fails takes SQL_ASCII the same results for windows (i used dependency walker to be sure i was using the right libpq.dll) -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL Asesoría y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157