Re: ereport bug

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dmitry Voronin <carriingfate92(at)yandex(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ereport bug
Date: 2015-01-14 19:12:00
Message-ID: CA+TgmobbajFdS63aDaX-719mFHmjXJsn2BV8+_OszqjNK07EZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 14, 2015 at 1:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Jan 12, 2015 at 6:27 AM, Dmitry Voronin
>> <carriingfate92(at)yandex(dot)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.
>
> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=1f9bf05e539646103c518bcbb49c04919b238f7a

Oops, sorry. I missed that.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-01-14 19:23:07 Re: INSERT ... ON CONFLICT UPDATE and RLS
Previous Message Dean Rasheed 2015-01-14 19:02:00 Re: INSERT ... ON CONFLICT UPDATE and RLS