Re: current breakage with PGCLIENTENCODING

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

I said:
> 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?

It occurs to me that the CVS-tip code tries to set client_encoding much
earlier in backend startup than was the case when this was driven by
a SET command issued by libpq after backend startup completed. However,
it works fine for me. Why isn't it working for you?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joachim Wieland 2003-04-27 07:46:17 Re: STABLE functions
Previous Message Tom Lane 2003-04-27 05:13:54 Re: current breakage with PGCLIENTENCODING