From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \encoding fixed |
Date: | 2003-08-02 02:44:59 |
Message-ID: | 200308020244.h722ixs06338@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
OK, psql docs updated to remove mention of that problem.
---------------------------------------------------------------------------
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Does the new protocol fix the fact that psql \encoding doesn't see SET
> > CLIENT_ENCODING changes.
>
> regression=# \encoding
> SQL_ASCII
> regression=# set client_encoding TO unicode;
> SET
> regression=# \encoding
> UNICODE
> regression=#
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-02 02:55:41 | Re: psql \encoding fixed |
Previous Message | Tom Lane | 2003-08-02 02:41:01 | Re: psql \encoding fixed |