Hello all
I see your patch, Tom. It works on my postgres 9.4 (intel x86_64). I write a
letter if I can test it on others platform.
Thank you!
14.01.2015, 21:40, "Tom Lane" :
> Robert Haas writes:
>> On Mon, Jan 12, 2015 at 6:27 AM, Dmitry Voronin
>> wrote:
>>> I am attaching to this lette
On Wed, Jan 14, 2015 at 1:40 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Mon, Jan 12, 2015 at 6:27 AM, Dmitry Voronin
>> 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 errfini
Robert Haas writes:
> On Mon, Jan 12, 2015 at 6:27 AM, Dmitry Voronin
> 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 i
On Mon, Jan 12, 2015 at 6:27 AM, Dmitry Voronin
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
Dmitry Voronin writes:
> Hello,
> postgresmen!I found incorrect execution of ereport()
> macro. If we pass into ereport() function 2 or more arguments, the
> macro errcontext does not correct execute. So, ereport() call stack
> is:errstarterrcontext_msg />set_errcontext_domainerrmsgerrfinish
Hello, postgresmen! I found incorrect execution of ereport() macro. If we pass into ereport() function 2 or more arguments, the macro errcontext does not correct execute. So, ereport() call stack is: errstarterrcontext_msgset_errcontext_domainerrmsgerrfinishpg_unreachable This bug causes that error
