Re: current breakage with PGCLIENTENCODING

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: current breakage with PGCLIENTENCODING
Date: 2003-04-30 03:47:42
Message-ID: 19446.1051674462@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> BTW, I have digged into the problem which pg_client_encoding() returns
> EUC_JP even psql starts up with PGCLIENTENCODING=SJIS.

Is it still there for you in CVS tip? I cannot reproduce it:

regression=# create database euc_jp encoding 'EUC_JP';
CREATE DATABASE
regression=# \q
$ PGCLIENTENCODING=SJIS psql euc_jp
Welcome to psql 7.4devel, the PostgreSQL interactive terminal.
... yadda yadda ...

euc_jp=# \encoding
SJIS
euc_jp=# show client_encoding ;
client_encoding
-----------------
SJIS
(1 row)

euc_jp=# select pg_client_encoding() ;
pg_client_encoding
--------------------
SJIS
(1 row)

I'm still wondering if you have a postgresql.conf or environment
setting that is affecting this.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2003-04-30 06:56:47 Re: FOR EACH STATEMENT triggers
Previous Message Philip Warner 2003-04-30 02:23:14 Re: "Adding missing from clause"