Re: BUG #5800: "corrupted" error messages (encoding problem ?)

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Carlo Curatolo <genamiga(at)brutele(dot)be>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Date: 2011-01-07 10:41:38
Message-ID: AANLkTi=bEaOZHajvwM+RAVim2CGoJKezuah9jPLwLTNu@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Dec 21, 2010 at 3:47 PM, Carlo Curatolo <genamiga(at)brutele(dot)be> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5800
> Logged by:          Carlo Curatolo
> Email address:      genamiga(at)brutele(dot)be
> PostgreSQL version: 9.0.2 64bits
> Operating system:   Windows 7 64bits
> Description:        "corrupted" error messages (encoding problem ?)
> Details:
>
> On a new PC I install only Windows (French) and PosgreSQL 9.0.2 with default
> parameters and without creating any object.
>
> Example of "corrupted" error messages that occurs on several client software
> (my own Java program, dbVisualizer, EMS SQL Manager)
>
> [Error Code: 0, SQL State: 42601]  ERREUR: erreur de syntaxe � la fin de
> l'entr�e
>
> 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]  ERREUR: erreur de syntaxe à la fin de
> l'entrée
>
> 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Page 2011-01-07 11:35:51 Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Previous Message Dave Page 2011-01-07 10:32:13 Re: BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"