Re: ereport bug - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ereport bug
Date
Msg-id CA+TgmobBYmnSnNFBO-gvx2x325kkPH=E8V=isRjud4DcZ2qJMQ@mail.gmail.com
Whole thread Raw
In response to ereport bug  (Dmitry Voronin <carriingfate92@yandex.ru>)
Responses Re: ereport bug
List pgsql-hackers
On Mon, Jan 12, 2015 at 6:27 AM, Dmitry Voronin
<carriingfate92@yandex.ru> wrote:
> I am attaching to this letter a test case that shows the behavior
> errcontext() macro and the way to fix it.

So the upshot of this is that given errfinish(A, B, C), where A, B,
and C are expressions, my gcc is choosing to evaluate C, then B, then
A, then the errfinish call itself.  But whoever wrote the errcontext()
macro evidently thought, in this kind of situation, the compiler would
be certain to evaluate A, then B, then C, then errfinish.  But it
doesn't.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
Next
From: Robert Haas
Date:
Subject: Re: s_lock.h default definitions are rather confused