From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Marc Cousin <cousinmarc(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5801: characters not encoded properly for column names |
Date: | 2010-12-28 11:49:20 |
Message-ID: | AANLkTinHcFEEcixUi0PhU6jG+2Zm4__v8z0wgfSeTCO4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Dec 28, 2010 at 4:01 AM, Marc Cousin <cousinmarc(at)gmail(dot)com> wrote:
> 2010/12/27 Robert Haas <robertmhaas(at)gmail(dot)com>:
>> On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin <cousinmarc(at)gmail(dot)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. :-(
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Ohnewald | 2010-12-28 12:19:55 | BUG #5802: configure script does not check for perl devel files |
Previous Message | Marc Cousin | 2010-12-28 09:01:01 | Re: BUG #5801: characters not encoded properly for column names |