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

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

2011/1/27 Génération Amiga <genamiga(at)brutele(dot)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

--
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 Oleg 2011-01-27 11:02:46 BUG #5852: Function date_trunc is not IMMUTABLE
Previous Message Mark 2011-01-27 01:24:18 BUG #5851: ROHS (read only hot standby) needs to be restarted manually in somecases.