Horton
Menu

Re: Do we still need MULE_INTERNAL?

Thomas Munro <thomas.munro@gmail.com>

View thread
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tatsuo Ishii <ishii@postgresql.org>, pgsql@j-davis.com, pgsql-hackers@lists.postgresql.org
Date: 2026-04-08T05:51:03Z
Lists: pgsql-hackers 
On Wed, Apr 8, 2026 at 5:32 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > Here's what I came up with for pg_upgrade.  It tests each database's
> > encodings with PG_VALID_BE_ENCODING(), and looks like this when it
> > fails:
> > ...
> > I'll wait a bit longer for this one, on the off chance of reviews at
> > this late hour.
>
> Passes a quick eyeball check, anyway.

Thanks!  And pushed.

Commits

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

  1. pg_upgrade: Check for unsupported encodings.

  2. Remove MULE_INTERNAL encoding.