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

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Susanne Ebrecht <susanne(at)2ndquadrant(dot)com>
Cc: genamiga(at)brutele(dot)be, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Date: 2011-01-07 13:11:06
Message-ID: AANLkTimOosRZOiSUDV6W9Vc0Bhv49SJpnq3mVP8go4mB@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 7, 2011 at 12:37 PM, Susanne Ebrecht
<susanne(at)2ndquadrant(dot)com> wrote:
> On 07.01.2011 12:35, Dave Page wrote:
>>
>> [Please keep messages on the mailing list]
>>
>> Hi,
>>
>> I don't see anything there that gives me any ideas. Anyone else have any
>> ideas?
>
> Hello,
>
> Yes.
>
> I would like to see output of CHCP.
> Which Windows codepage is used? 850?

In our testing, the windows codepage was 1252, and the console
codepage was 850 (giving the normal warning about the mismatch that
we've seen for years). That was the case on installations with, and
without the incorrect formatting.

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

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Leif Gunnar Erlandsen 2011-01-07 14:14:14 BUG #5820: FATAL: could not access file "libpqwalreceiver": No such file or directory
Previous Message Gouse 2011-01-07 12:58:19 Re: to_timestamp returns the incorrect result for the DST fall over time.