Thread: psql \encoding fixed
Does the new protocol fix the fact that psql \encoding doesn't see SET CLIENT_ENCODING changes. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
Bruce Momjian <pgman@candle.pha.pa.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
OK, psql docs updated to remove mention of that problem. --------------------------------------------------------------------------- Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> OK, psql docs updated to remove mention of that problem.
They already were, I thought.
regards, tom lane
Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > OK, psql docs updated to remove mention of that problem. > > They already were, I thought. It was still mentioned in the psql manual page. I know because I added it in 7.3, and it was still there. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073