David Rowley <[email protected]> writes:
> On Mon, 6 Jul 2026 at 03:18, Tom Lane <[email protected]> wrote:
>> It came to my attention just now that 59c2f03d1 adjusted ereport()
>> to be MSVC-friendly, but did not touch plpy_elog.h's PLy_elog(),
>> which has a borrowed copy of the same logic. Was that intentional?
> That was unintentional and caused by my unawareness of that version of
> the macro.
>> It seems like we should keep those looking alike.
> Agreed.
Cool. You wanna fix it, or shall I?
regards, tom lane
