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

2011-01-03 Thread Marc Cousin
The Tuesday 28 December 2010 12:49:20, Robert Haas wrote : > On Tue, Dec 28, 2010 at 4:01 AM, Marc Cousin wrote: > > 2010/12/27 Robert Haas : > >> On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin wrote: > >>> With the Windows server : > >>> test=# SET client_encoding TO 'win1252'; > >>> SET > >> >

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

2010-12-28 Thread Robert Haas
On Tue, Dec 28, 2010 at 4:01 AM, Marc Cousin wrote: > 2010/12/27 Robert Haas : >> On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin wrote: >>> With the Windows server : >>> test=# SET client_encoding TO 'win1252'; >>> SET >> >> I have a vague recollection that the argument to SET client_encoding >> is

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

2010-12-28 Thread Marc Cousin
2010/12/27 Robert Haas : > On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin 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 doe

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

2010-12-27 Thread Robert Haas
On Thu, Dec 23, 2010 at 5:18 AM, Marc Cousin 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'

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

2010-12-23 Thread Marc Cousin
Le jeudi 23 décembre 2010 18:21:55, John R Pierce a écrit : > On 12/23/10 2:34 AM, Marc Cousin wrote: > > No, from a Linux psql client (inside a kde konsole). You can setup any > > charset in it. I have exactly the same behaviour with psql under windows > > anyway, with a chcp 1252 in the cmd conso

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

2010-12-23 Thread John R Pierce
On 12/23/10 2:34 AM, Marc Cousin wrote: No, from a Linux psql client (inside a kde konsole). You can setup any charset in it. I have exactly the same behaviour with psql under windows anyway, with a chcp 1252 in the cmd console. It's not a console charset problem, I've tripled checked that :) An

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

2010-12-23 Thread Marc Cousin
No, from a Linux psql client (inside a kde konsole). You can setup any charset in it. I have exactly the same behaviour with psql under windows anyway, with a chcp 1252 in the cmd console. It's not a console charset problem, I've tripled checked that :) And anyway, this character shouldn't get

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

2010-12-23 Thread Pavel Stehule
Hello Marc, It was entered from a windows cmd console? It doesn't use win encodings as default. For example, it must be executed with parameter /c chcp 1250 for win1250 encoding. Regards Pavel Stehule 2010/12/23 Marc Cousin : > > The following bug has been logged online: > > Bug reference:    

[BUGS] BUG #5801: characters not encoded properly for column names

2010-12-23 Thread Marc Cousin
The following bug has been logged online: Bug reference: 5801 Logged by: Marc Cousin Email address: cousinm...@gmail.com PostgreSQL version: 9.0.2 Operating system: Windows XP Description:characters not encoded properly for column names Details: I get a different be