Re: Do we still need MULE_INTERNAL?

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>

To: thomas.munro@gmail.com

Cc: pgsql@j-davis.com, pgsql-hackers@lists.postgresql.org, tgl@sss.pgh.pa.us

Date: 2026-04-03T00:06:40Z

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pg_upgrade: Check for unsupported encodings.
- ce11e63f812f 19 (unreleased) landed
Remove MULE_INTERNAL encoding.
- 77645d44e355 19 (unreleased) landed