Re: BUG #14679: Inconsistent/wrong behavior of pg_trigger_depth when used with DEFERRED CONSTRAINTS

From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14679: Inconsistent/wrong behavior of pg_trigger_depth when used with DEFERRED CONSTRAINTS
Date: 2017-05-30 14:11:46
Message-ID: f5301348-2451-4793-bb4c-0704ba4c4a8d@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 30/05/2017 17:03, Tom Lane wrote:
> achill(at)matrix(dot)gatewaynet(dot)com writes:
>> I just run into a behavior that I consider wrong. Test case :
> Isn't this the same thing you already filed in
> <3d1a5143-389c-256a-cda9-44ca002fc606(at)matrix(dot)gatewaynet(dot)com>?
Yes, I just thought that it went unnoticed , so I tried the official method.
>
> Duplicate bug reports just confuse matters.
Won't happen again. Thanks for taking care of this.
>
> regards, tom lane

--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Flo 2017-05-30 15:02:53 Re: Can't restore view with pg_restore
Previous Message Tom Lane 2017-05-30 14:03:23 Re: BUG #14679: Inconsistent/wrong behavior of pg_trigger_depth when used with DEFERRED CONSTRAINTS