| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-patches(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: prevent encoding conversion recursive error |
| Date: | 2005-08-09 02:51:27 |
| Message-ID: | 11566.1123555887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
I wrote:
> This does not look real easy to fix. Who's up for reimplementing
> gettext and a few other pieces from scratch?
However, I did find
which leads to the question "why aren't we using
bind_textdomain_codeset() to tell gettext what character set it should
produce"?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-08-09 03:07:53 | Re: Simplifying wal_sync_method |
| Previous Message | Tom Lane | 2005-08-09 02:34:14 | Re: prevent encoding conversion recursive error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | yuanjia lee | 2005-08-09 03:46:40 | Allow WAL information to recover corrupted pg_controldata patch |
| Previous Message | Tom Lane | 2005-08-09 02:34:14 | Re: prevent encoding conversion recursive error |