The Tuesday 28 December 2010 12:49:20, Robert Haas wrote : > On Tue, Dec 28, 2010 at 4:01 AM, Marc Cousin <cousinm...@gmail.com> wrote: > > 2010/12/27 Robert Haas <robertmh...@gmail.com>: > >> On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin <cousinm...@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'; > > > > Here it is… > > > > postgres=# 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 ? > > Hrm, OK. Well, you just used up my one guess. :-(
Sorry about that. Anyone else wanting to take a guess ? :) -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
