Re: BUG #5801: characters not encoded properly for column names

2010/12/27 Robert Haas <robertmhaas@gmail.com>:
> On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin <cousinmarc@gmail.com> wrote:
>> With the Windows server :
>> test=3D# 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. =A0Am I wrong? =A0What happens if
> you do:
>
> SET client_encoding TO
> 'some_really_long_string_that_is_almost_certainly_not_a_valid_encoding';

Here it is=85

postgres=3D# SET client_encoding TO 'foo';
ERROR:  invalid value for parameter "client_encoding": "foo"

(It does the same with your really long string by the way :) )

Seems validated to me ?