Request a Demo
Home   >   mailing lists

Re: Fixing MSVC's inability to detect elog(ERROR) does not return - Mailing list pgsql-hackers

From David Rowley
Subject Re: Fixing MSVC's inability to detect elog(ERROR) does not return
Date
Msg-id CAApHDvr2+Gc5uuE3LvQqF4U3OoQLWkxSH7hhVUttz9fpAQ5iyA@mail.gmail.com
Whole thread
In response to Re: Fixing MSVC's inability to detect elog(ERROR) does not return  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing MSVC's inability to detect elog(ERROR) does not return
List pgsql-hackers
Tree view 
On Mon, 6 Jul 2026 at 03:18, Tom Lane <tgl@sss.pgh.pa.us> 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.

David

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: ri_Fast* crash w/ nullable UNIQUE constraint
Next
From: Jeremy Schneider
Date:
Subject: hang during shutdown