From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | Scot Kreienkamp <Scot(dot)Kreienkamp(at)la-z-boy(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "depesz(at)depesz(dot)com" <depesz(at)depesz(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug |
Date: | 2025-08-20 20:03:52 |
Message-ID: | 33B10D6F-5120-4DE8-9725-CAF993B2A0F8@gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 20 Aug 2025, at 14:03, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alban Hertroys <haramrae(at)gmail(dot)com> writes:
>> Or is it just my end that turns Scott's (and only Scott's) messages into gibberish Chinese?
>
> 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’s 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’s 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2025-08-20 20:14:56 | Re: MS SQL to Postgres |
Previous Message | Adrian Klaver | 2025-08-20 17:56:49 | Re: MS SQL to Postgres |