Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: Streaming replica hangs periodically for ~ 1 second - how to
 diagnose/debug
From: Alban Hertroys <haramrae@gmail.com>
In-Reply-To: <988958.1755691419@sss.pgh.pa.us>
Date: Wed, 20 Aug 2025 22:03:52 +0200
Cc: Adrian Klaver <adrian.klaver@aklaver.com>,
 "depesz@depesz.com" <depesz@depesz.com>,
 PostgreSQL General <pgsql-general@lists.postgresql.org>,
 Tom Lane <tgl@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Message-Id: <33B10D6F-5120-4DE8-9725-CAF993B2A0F8@gmail.com>
References: <aKSyq74zIuLS-2B5@depesz.com>
 <d1d40328-ae3a-4089-9ee0-beade92d7c45@aklaver.com>
 <a2cd8084-b93e-4da0-8999-569a6e58ef6b.8f62f83c-ab51-428e-98d1-ab1abb243a49.93a25b3a-0b25-4d18-8a69-08f841e737cb@emailsignatures365.codetwo.com>
 <a2cd8084-b93e-4da0-8999-569a6e58ef6b.b1460fbe-55a2-4060-995f-39f4e2f3c7f9.5415824a-634b-472f-8c56-ab10d48e91f7@emailsignatures365.codetwo.com>
 <SJ0PR15MB5245919B78ECB02696ADD1959A30A@SJ0PR15MB5245.namprd15.prod.outlook.com>
 <8B89FABB-E020-4EF0-9019-08B1B9E22208@gmail.com>
 <988958.1755691419@sss.pgh.pa.us>
To: Scot Kreienkamp <Scot.Kreienkamp@la-z-boy.com>
Archived-At: <https://www.postgresql.org/message-id/33B10D6F-5120-4DE8-9725-CAF993B2A0F8%40gmail.com>
Precedence: bulk


> On 20 Aug 2025, at 14:03, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> Alban Hertroys <haramrae@gmail.com> writes:
>> Or is it just my end that turns Scott's (and only Scott's) messages =
into gibberish Chinese?
>=20
> What it looks like from here is that the message body is in UTF16:
> every other byte is zero.  That gives my email client indigestion,
> too.

Actually, I think it=E2=80=99s misreporting the message content as =
UTF-16, while it is in fact encoded as UTF-8. So the error appears to be =
on the sender side.

Apparently, Apple Mail.app is rather strict about following the reported =
encoding, while Gmail for example does some attempt to guess. That would =
explain the less terrible results with Gmail.

I can base64 decode the message just fine on the command line, which =
runs in a terminal emulator (Apple=E2=80=99s Terminal.app) that does =
handle UTF-8, but not UTF-16 by default.

Alban Hertroys
--
Illustratief voor het verschil tussen steek- en snijwapens:
Met mensen die een punthoofd hebben,
kun je goed de draak steken.
Met mensen die scherp zijn,
lukt dat juist slecht.