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 AANLkTi=bEaOZHajvwM+RAVim2CGoJKezuah9jPLwLTNu@mail.gmail.com
Whole thread Raw
In response to BUG #5800: "corrupted" error messages (encoding problem ?)  ("Carlo Curatolo" <genamiga@brutele.be>)
List pgsql-bugs
On Tue, Dec 21, 2010 at 3:47 PM, Carlo Curatolo <genamiga@brutele.be> wrote:
>
> 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 (encod=
ing problem ?)
> Details:
>
> On a new PC I install only Windows (French) and PosgreSQL 9.0.2 with defa=
ult
> parameters and without creating any object.
>
> Example of "corrupted" error messages that occurs on several client softw=
are
> (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.

--=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 #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"
Next
From: Dave Page
Date:
Subject: Re: BUG #5800: "corrupted" error messages (encoding problem ?)