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=bjYRQ=KTuj=bsUz7mAZ--vL7bA3o8b94xN8To@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 ?)  (genamiga <genamiga@brutele.be>)
List pgsql-bugs
2011/1/27 G=E9n=E9ration Amiga <genamiga@brutele.be>:
> Hello Dave,
>
> Any news about that encoding problem ?

We've been working with a couple of our friends in Japan, and it looks
like one of them has tracked down an issue in the gettext library. It
looks like we can work around it. We'l try to get it into the next
release.

> Our messages don't appear on the "pgsql-bugs" web page...
> How can I do that ?

Yes they do: http://archives.postgresql.org/pgsql-bugs/2010-12/msg00156.php

--=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: "Mark"
Date:
Subject: BUG #5851: ROHS (read only hot standby) needs to be restarted manually in somecases.
Next
From: "Oleg"
Date:
Subject: BUG #5852: Function date_trunc is not IMMUTABLE