| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | thomas(dot)munro(at)gmail(dot)com |
| Cc: | pgsql(at)j-davis(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Subject: | Re: Do we still need MULE_INTERNAL? |
| Date: | 2026-04-03 00:06:40 |
| Message-ID: | 20260403.090640.487260902102768591.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas,
It seems there's remaining "Mule internal" in
doc/src/sgml/charset.sgml in your patch.
<para>
The character set support in <productname>PostgreSQL</productname>
allows you to store text in a variety of character sets (also called
encodings), including
single-byte character sets such as the ISO 8859 series and
multiple-byte character sets such as <acronym>EUC</acronym> (Extended Unix
Code), UTF-8, and Mule internal code. All supported character sets
~~~~~~~~~~~~~~~~~~
Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2026-04-03 00:07:40 | Re: pg_waldump: support decoding of WAL inside tarfile |
| Previous Message | surya poondla | 2026-04-02 23:51:09 | Re: heapam_tuple_complete_speculative : remove unnecessary tuple fetch |