v7.3 : \encoding doesn't show changes in client encoding that are not done with \encoding itself (i.e. set names/set client_encoding)

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: pgsql-bugs(at)postgresql(dot)org
Subject: v7.3 : \encoding doesn't show changes in client encoding that are not done with \encoding itself (i.e. set names/set client_encoding)
Date: 2002-12-15 11:02:40
Message-ID: 200212151202.40513.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

L.S.

It seems that '\encoding' only shows the correct client encoding if any
changes are applied by using '\encoding' itself.

If the client encoding is changed by using 'set names' or 'set
client_encoding', the result of '\encoding' will still be the old one used.
However, the encoding seems to be changed, as 'show client_encoding' will
show.

Regards,

Frank van Vugt

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Neil Conway 2002-12-16 05:36:35 Re: Bug #848: Index on bigint column is unused in selects
Previous Message pgsql-bugs 2002-12-14 20:33:00 Bug #848: Index on bigint column is unused in selects

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2002-12-17 06:49:48 updated PITR patch
Previous Message Bruce Momjian 2002-12-14 18:49:47 Re: postmaster segfaults when pg_hba.cof is missing