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

The Tuesday 28 December 2010 12:49:20, Robert Haas wrote :
> On Tue, Dec 28, 2010 at 4:01 AM, Marc Cousin <cousinmarc@gmail.com> wrote:
> > 2010/12/27 Robert Haas <robertmhaas@gmail.com>:
> >> On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin <cousinmarc@gmail.com>=20
wrote:
> >>> With the Windows server :
> >>> test=3D# SET client_encoding TO 'win1252';
> >>> SET
> >>=20
> >> 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:
> >>=20
> >> SET client_encoding TO
> >> 'some_really_long_string_that_is_almost_certainly_not_a_valid_encoding=
';
> >=20
> > Here it is=85
> >=20
> > postgres=3D# SET client_encoding TO 'foo';
> > ERROR:  invalid value for parameter "client_encoding": "foo"
> >=20
> > (It does the same with your really long string by the way :) )
> >=20
> > Seems validated to me ?
>=20
> Hrm, OK.  Well, you just used up my one guess.  :-(

Sorry about that. Anyone else wanting to take a guess ? :)