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

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-27 21:56:32
Message-ID: AANLkTikiF8SA3JHK8tg7DbycQy0jGUKo=r4cJrX3MTnn@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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';

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-12-27 21:58:13 Re: BUG #5796: Problem with history-files
Previous Message Robert Haas 2010-12-27 21:41:03 Re: BUG #5797: Strange bug with hstore