Skip site navigation (1) Skip section navigation (2)

Re: BUG #6452: psql: can't change client encoding from the command line

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: felix(dot)gerzaguet(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6452: psql: can't change client encoding from the command line
Date: 2012-02-14 12:41:14
Message-ID: 4F3A566A.9060606@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On 11.02.2012 20:02, felix(dot)gerzaguet(at)gmail(dot)com wrote:
> Using the command line, I can't change the client encoding, but I can change
> it using the "\encoding" command :
>
> C:\>psql --variable=ENCODING=UTF8
> could not find a "psql" to execute
> could not find a "psql" to execute
> psql (9.1.2)
> WARNING: Console code page (850) differs from Windows code page (1252)
>           8-bit characters might not work correctly. See psql reference
>           page "Notes for Windows users" for details.
> Type "help" for help.
>
> postgres=# \encoding
> WIN1252
> postgres=# \echo :ENCODING
> WIN1252
> postgres=# \encoding UTF8
> postgres=# \encoding
> UTF8
> postgres=# \echo :ENCODING
> UTF8
> postgres=# \q

Yeah, "\set ENCODING UTF8" doesn't seem to work either. The "ENCODING" 
psql variable tracks changes to the server's client_encoding setting, 
but not vice versa. That probably should be fixed, or at least it should 
throw an error telling the user to use \encoding instead.

As a workaround, you can set the PGCLIENTENCODING environment variable 
before launching psql.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: albert.cieszkowskiDate: 2012-02-14 13:20:43
Subject: BUG #6457: Regexp not processing word (with special characters onends) correctly (UTF-8)
Previous:From: tmpfsDate: 2012-02-13 16:50:20
Subject: BUG #6456: no password

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group