Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sun, 14 Aug 2005 23:03:56 +0200
- Message-id: <200508142303.57215.peter_e@gmx.net> <text/plain>
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.
- Follow-Ups:
- Re: prevent encoding conversion recursive error
- From: Tom Lane
- Re: prevent encoding conversion recursive error
- References:
- prevent encoding conversion recursive error
- From: Qingqing Zhou
- Re: prevent encoding conversion recursive error
- From: Tom Lane
- Re: prevent encoding conversion recursive error
- From: Tom Lane
- prevent encoding conversion recursive error
- Prev by Date: Re: createuser patch
- Next by Date: Re: prevent encoding conversion recursive error
- Previous by thread: Re: prevent encoding conversion recursive error
- Next by thread: Re: prevent encoding conversion recursive error
- Indexes: