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

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Дата
Msg-id AANLkTimOosRZOiSUDV6W9Vc0Bhv49SJpnq3mVP8go4mB@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #5800: "corrupted" error messages (encoding problem ?)  (Susanne Ebrecht <susanne@2ndQuadrant.com>)
Список pgsql-bugs
On Fri, Jan 7, 2011 at 12:37 PM, Susanne Ebrecht
<susanne@2ndquadrant.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Gouse
Дата:
Сообщение: Re: to_timestamp returns the incorrect result for the DST fall over time.
Следующее
От: "Leif Gunnar Erlandsen"
Дата:
Сообщение: BUG #5820: FATAL: could not access file "libpqwalreceiver": No such file or directory