Re: BUG #5800: "corrupted" error messages (encoding problem ?) - Mailing list pgsql-bugs

From Dave Page
Subject Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Date
Msg-id AANLkTikim9mmysM_On_RicKVuOERi-aw0MaRTPFXVD4j@mail.gmail.com
Whole thread Raw
In response to BUG #5800: "corrupted" error messages (encoding problem ?)  ("Carlo Curatolo" <genamiga@brutele.be>)
Responses Re: BUG #5800: "corrupted" error messages (encoding problem ?)  (Susanne Ebrecht <susanne@2ndQuadrant.com>)
List pgsql-bugs
[Please keep messages on the mailing list]

Hi,

I don't see anything there that gives me any ideas. Anyone else have any id=
eas?

2011/1/7 G=C3=A9n=C3=A9ration Amiga <genamiga@brutele.be>:
> Hello Dave,
>
> Here are the result of "\! set" on the servers and I still have W7-32 and=
 W7-64 (WinXP died)
> **************
> W7-64 and PG9-64
> **************
> postgres=3D# \! set;
> =3D::=3D::\
> =3DC:=3DC:\Program Files\PostgreSQL\9.0\scripts
> ALLUSERSPROFILE=3DC:\ProgramData
> APPDATA=3DC:\Users\Carlo\AppData\Roaming
> CLIENTENCODING_JP=3D0
> CommonProgramFiles=3DC:\Program Files\Common Files
> CommonProgramFiles(x86)=3DC:\Program Files (x86)\Common Files
> CommonProgramW6432=3DC:\Program Files\Common Files
> COMPUTERNAME=3DWIN7-64
> ComSpec=3DC:\Windows\system32\cmd.exe
> database=3Dpostgres
> FP_NO_HOST_CHECK=3DNO
> HOMEDRIVE=3DC:
> HOMEPATH=3D\Users\Carlo
> LOCALAPPDATA=3DC:\Users\Carlo\AppData\Local
> LOGONSERVER=3D\\WIN7-64
> NUMBER_OF_PROCESSORS=3D2
> OS=3DWindows_NT
> Path=3DC:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows=
\System32\WindowsPowerShell\v1.0\
> PATHEXT=3D.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
> PGLOCALEDIR=3DC:/Program Files/PostgreSQL/9.0/share/locale
> PGSYSCONFDIR=3DC:/Program Files/PostgreSQL/9.0/etc
> port=3D5432
> PROCESSOR_ARCHITECTURE=3DAMD64
> PROCESSOR_IDENTIFIER=3DIntel64 Family 6 Model 15 Stepping 6, GenuineIntel
> PROCESSOR_LEVEL=3D6
> PROCESSOR_REVISION=3D0f06
> ProgramData=3DC:\ProgramData
> ProgramFiles=3DC:\Program Files
> ProgramFiles(x86)=3DC:\Program Files (x86)
> ProgramW6432=3DC:\Program Files
> PROMPT=3D$P$G
> PSModulePath=3DC:\Windows\system32\WindowsPowerShell\v1.0\Modules\
> PUBLIC=3DC:\Users\Public
> server=3Dlocalhost
> SESSIONNAME=3DConsole
> SystemDrive=3DC:
> SystemRoot=3DC:\Windows
> TEMP=3DC:\Users\Carlo\AppData\Local\Temp
> TMP=3DC:\Users\Carlo\AppData\Local\Temp
> USERDOMAIN=3DWIN7-64
> USERNAME=3Dpostgres
> USERPROFILE=3DC:\Users\Carlo
> windir=3DC:\Windows
> postgres=3D#
>
> **************
> W7-32 and PG9-32
> **************
> postgres=3D# \! set;
> =3D::=3D::\
> =3DC:=3DC:\Program Files\PostgreSQL\9.0\scripts
> ALLUSERSPROFILE=3DC:\ProgramData
> APPDATA=3DC:\Users\Carlo\AppData\Roaming
> CLIENTENCODING_JP=3D0
> CommonProgramFiles=3DC:\Program Files\Common Files
> COMPUTERNAME=3DWIN7-32
> ComSpec=3DC:\Windows\system32\cmd.exe
> database=3Dpostgres
> FP_NO_HOST_CHECK=3DNO
> HOMEDRIVE=3DC:
> HOMEPATH=3D\Users\Carlo
> LOCALAPPDATA=3DC:\Users\Carlo\AppData\Local
> LOGONSERVER=3D\\WIN7-32
> NUMBER_OF_PROCESSORS=3D1
> OS=3DWindows_NT
> Path=3DC:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows=
\System32\WindowsPowerShell\v1.0\
> PATHEXT=3D.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
> PGLOCALEDIR=3DC:/Program Files/PostgreSQL/9.0/share/locale
> PGSYSCONFDIR=3DC:/Program Files/PostgreSQL/9.0/etc
> port=3D5432
> PROCESSOR_ARCHITECTURE=3Dx86
> PROCESSOR_IDENTIFIER=3Dx86 Family 15 Model 2 Stepping 4, GenuineIntel
> PROCESSOR_LEVEL=3D15
> PROCESSOR_REVISION=3D0204
> ProgramData=3DC:\ProgramData
> ProgramFiles=3DC:\Program Files
> PROMPT=3D$P$G
> PSModulePath=3DC:\Windows\system32\WindowsPowerShell\v1.0\Modules\
> PUBLIC=3DC:\Users\Public
> server=3Dlocalhost
> SESSIONNAME=3DConsole
> SystemDrive=3DC:
> SystemRoot=3DC:\Windows
> TEMP=3DC:\Users\Carlo\AppData\Local\Temp
> TMP=3DC:\Users\Carlo\AppData\Local\Temp
> USERDOMAIN=3DWin7-32
> USERNAME=3Dpostgres
> USERPROFILE=3DC:\Users\Carlo
> windir=3DC:\Windows
> postgres=3D#
> ***********************************************
> I can send you whatever you need, I don't touch anything to those servers=
. I use them only for testing and I have image backups.
>
> Best regards.
>
> Curatolo Carlo
>
> =3D =3D =3D =3D =3D =3D =3D =3D Message d'origine du 2011-01-07 =C3=A0 11=
:41:30 =3D =3D =3D =3D =3D =3D =3D =3D
> On Tue, Dec 21, 2010 at 3:47 PM, Carlo Curatolo <genamiga@brutele.be> wro=
te:
>>
>> The following bug has been logged online:
>>
>> Bug reference: =C2=A0 =C2=A0 =C2=A05800
>> Logged by: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Carlo Curatolo
>> Email address: =C2=A0 =C2=A0 =C2=A0genamiga@brutele.be
>> PostgreSQL version: 9.0.2 64bits
>> Operating system: =C2=A0 Windows 7 64bits
>> Description: =C2=A0 =C2=A0 =C2=A0 =C2=A0"corrupted" error messages (enco=
ding problem ?)
>> Details:
>>
>> On a new PC I install only Windows (French) and PosgreSQL 9.0.2 with def=
ault
>> parameters and without creating any object.
>>
>> Example of "corrupted" error messages that occurs on several client soft=
ware
>> (my own Java program, dbVisualizer, EMS SQL Manager)
>>
>> [Error Code: 0, SQL State: 42601] =C2=A0ERREUR: erreur de syntaxe =EF=BF=
=BD la fin de
>> l'entr=EF=BF=BDe
>>
>> Test 1 : Windows 7 64 bits and PosgreSQL 9.0.2 64 bits
>>
>> ... the problem occurs
>>
>> Test 2 : Windows 7 64 bits and PosgreSQL 9.0.2 32 bits
>>
>> ... the problem occurs
>>
>> Test 3 : Windows 7 32 bits and PosgreSQL 9.0.2 32 bits
>>
>> ... NO problem, the error message is correct
>> [Error Code: 0, SQL State: 42601] =C2=A0ERREUR: erreur de syntaxe =C3=A0=
 la fin de
>> l'entr=C3=A9e
>>
>> This issue occurs only when PostgreSQL 9.0.2 is installed on Windows 7 64
>> bits...
> FYI, we've been investigating this, however, whilst we can reproduce
> the same issue, we see it in different circumstances which conflict
> with yours:
> You reported:
> 64 bit OS, 64 bit PG - corruption
> 64 bit OS, 32 bit PG - corruption
> 32 bit OS, 32 bit PG - OK
> We see:
> 64 bit OS, 64 bit PG - OK
> 64 bit OS, 32 bit PG - corruption
> 32 bit OS, 32 bit PG - corruption
> That implies to us that this is something environmental, rather than a
> build or installer bug (between us, both installers work correctly on
> their native platforms).
> What does the environment look like on both of your servers? Try
> running "\! set" from a psql session in each.
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
> -----
> Aucun virus trouv=C3=A9 dans ce message.
> Analyse effectu=C3=A9e par AVG - www.avg.fr
> Version: 10.0.1191 / Base de donn=C3=A9es virale: 1435/3364 - Date: 06/01=
/2011
>
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D



--=20
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Dave Page
Date:
Subject: Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Next
From: Susanne Ebrecht
Date:
Subject: Re: BUG #5800: "corrupted" error messages (encoding problem ?)