| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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 18:40:01 |
| Message-ID: | 11429.1421260801@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daurnimator | 2015-01-14 18:53:02 | Re: libpq bad async behaviour |
| Previous Message | Peter Geoghegan | 2015-01-14 17:42:24 | Re: hung backends stuck in spinlock heavy endless loop |