Request a Demo
Home   >   mailing lists

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

From Tom Lane
Subject Re: Fixing MSVC's inability to detect elog(ERROR) does not return
Date
Msg-id 754534.1783264708@sss.pgh.pa.us
Whole thread
In response to Re: Fixing MSVC's inability to detect elog(ERROR) does not return  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Fixing MSVC's inability to detect elog(ERROR) does not return
List pgsql-hackers
Tree view 
David Rowley <dgrowleyml@gmail.com> writes:
> Now pushed and awaiting buildfarm feedback.

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?
It seems like we should keep those looking alike.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Sehrope Sarkuni
Date:
Subject: Re: inconsistent jsonb 'null' conversions
Next
From: Pavel Stehule
Date:
Subject: Re: POC: PLpgSQL FOREACH IN JSON ARRAY