Re: user names & non-ASCII

From: "Pavel Holec" <holec(at)email(dot)cz>
To: "'Pavel Stehule'" <pavel(dot)stehule(at)gmail(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: user names & non-ASCII
Date: 2011-12-16 13:21:43
Message-ID: !&!
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-bugs

PGCLIENTENCODING='latin2' - doesn't help (SetEnvironmentVariable)
SET CLIENT_ENCODING TO - doesn't help (too late)
connect with "only ascii" not possible (users are set)
SET role TO specialcharsrole? google doesn't know
On servers we have 8.4.7 not 9.1.1
In manual is PQconnectdb() with options="client_encoding =..." doesn't work


-----Original Message-----
From: Pavel Stehule [mailto:pavel(dot)stehule(at)gmail(dot)com]
Sent: Friday, December 16, 2011 12:18 AM
To: Pavel Holec
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] user names & non-ASCII


this is not bug

you can try use a system variable PGCLIENTENCODING

bash-4.2$ PGCLIENTENCODING='latin2' psql postgres psql (9.1.1) Type "help" for help.

postgres=# show client_encoding ;
(1 row)

other way is connect with "only ascii" user name, changing encoding and changin current role

SET role TO specialcharsrole;


Pavel Stehule

2011/12/16 Pavel Holec <holec(at)email(dot)cz>:
> Hi All, please help.
> I Have PostgreSQL server 8.4.9 on Linux, database utf-8 and Client app
> on Windows (VC++ and libpq.dll).
> I need to use user account with non-ASCII and PQconnectdb() with
> options="client_encoding=WIN1250" doesn't work.
> SET CLIENT_ENCODING TO 'WIN1250' after PQconnectdb is too late because
> connection fails.
> Best regards,
> Pavel Holec

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrea Grassi 2011-12-16 14:10:47 R: BUG #6342: libpq blocks forever in "poll" function
Previous Message Havasvölgyi Ottó 2011-12-16 12:50:03 Re: Postgresql 9.1.2 - abnormal memory usage