Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w8S3z-000XpR-1L for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Apr 2026 00:07:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w8S3y-008vBR-0C for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Apr 2026 00:07:02 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w8S3x-008vBJ-1q for pgsql-hackers@lists.postgresql.org; Fri, 03 Apr 2026 00:07:02 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w8S3u-00000000Gfl-3jJF for pgsql-hackers@lists.postgresql.org; Fri, 03 Apr 2026 00:07:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=S4ejDpY1w37DBdeGadgc/ib4WMgBWZK0+ZRGZ6L8PP4=; b=OYnJ4eIawcifSDC7Tez2bgMqkl wFFVNhsAbmz1DlTDHhT+hfcGfqT86cqM0P+U1PYW3X8Fb0yigA6s4K2CSUc5g6gzldVaNsnpDJJmy jHY48Of0Tc8LssGIi3AS7nBnXGyP7bqrbkfY2ocQfdczp7BYeYDl15VXUuelPoahbHZC7fG4zjgUw k7Nhp7XIJIA2qgc7YU9h9BzYNhPzl1p3EdW+7lLaOTKddGEzeX8mqwTgijvcTrj0rIYwuVjnJZAPw CHlkJ3yaDlbi7GeXkwriR99TSSntYBwCg/sHNLD0L6NTy43uqWhmnREYP/AKHtwuWBfuF0Yxdby4i jP8m3dDQ==; Received: from [2409:11:4120:300:bba:a076:86e7:5c41] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w8S3n-000cIV-1T; Fri, 03 Apr 2026 00:06:56 +0000 Date: Fri, 03 Apr 2026 09:06:40 +0900 (JST) Message-Id: <20260403.090640.487260902102768591.ishii@postgresql.org> To: thomas.munro@gmail.com Cc: pgsql@j-davis.com, pgsql-hackers@lists.postgresql.org, tgl@sss.pgh.pa.us Subject: Re: Do we still need MULE_INTERNAL? From: Tatsuo Ishii In-Reply-To: <20260402.075006.1215979483410908859.ishii@postgresql.org> References: <20260401.083826.1947227822512469454.ishii@postgresql.org> <790a2e194c2d8cb03a2f1b8b580b64f25a5095b0.camel@j-davis.com> <20260402.075006.1215979483410908859.ishii@postgresql.org> X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:bba:a076:86e7:5c41 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas, It seems there's remaining "Mule internal" in doc/src/sgml/charset.sgml in your patch. The character set support in PostgreSQL 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 EUC (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