Re: prevent encoding conversion recursive error

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-patches(at)postgresql(dot)org
Subject: Re: prevent encoding conversion recursive error
Date: 2005-08-14 21:03:56
Message-ID: 200508142303.57215.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Am Dienstag, 9. August 2005 04:51 schrieb Tom Lane:
> which leads to the question "why aren't we using
> bind_textdomain_codeset() to tell gettext what character set it should
> produce"?

That would probably require us to solve the question on how to translate
PostgreSQL encoding names to OS encoding names.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2005-08-14 21:12:23 Re: small proposal: pg_config record flag variables?
Previous Message Thomas F. O'Connell 2005-08-14 19:45:21 Re: Simplifying wal_sync_method

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-08-14 21:48:14 Re: prevent encoding conversion recursive error
Previous Message Tom Lane 2005-08-14 20:17:32 Re: createuser patch