Re: BUG #5801: characters not encoded properly for column names - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5801: characters not encoded properly for column names
Date
Msg-id AANLkTikiF8SA3JHK8tg7DbycQy0jGUKo=r4cJrX3MTnn@mail.gmail.com
Whole thread Raw
In response to BUG #5801: characters not encoded properly for column names  ("Marc Cousin" <cousinmarc@gmail.com>)
Responses Re: BUG #5801: characters not encoded properly for column names  (Marc Cousin <cousinmarc@gmail.com>)
List pgsql-bugs
On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin <cousinmarc@gmail.com> wrote:
> With the Windows server :
> test=# SET client_encoding TO 'win1252';
> SET

I have a vague recollection that the argument to SET client_encoding
isn't validated on Windows, and if you enter a value that it doesn't
like it simply silently doesn't work.  Am I wrong?  What happens if
you do:

SET client_encoding TO
'some_really_long_string_that_is_almost_certainly_not_a_valid_encoding';

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #5797: Strange bug with hstore
Next
From: Robert Haas
Date:
Subject: Re: BUG #5796: Problem with history-files