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-27 05:13:54
Message-ID: 22758.1051420434@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:
> As you can see, the result of "show client_encoding;" and "select
> pg_client_encoding();" do not match.

Weird, it works fine for me:

$ PGCLIENTENCODING=SJIS psql regression
Welcome to psql 7.4devel, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit

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

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

I would not have been real surprised to hear that psql's \encoding is
out of sync, but it *does* surprise me that "show client_encoding" might
not match pg_client_encoding(). I would think those are looking at the
same backend state variable. Any theory how that could happen?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-04-27 05:28:46 Re: current breakage with PGCLIENTENCODING
Previous Message Tom Lane 2003-04-27 05:06:01 Re: Array access to type "name"