From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andrew Gierth <rhodiumtoad(at)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
Subject: | Re: BUG #14808: V10-beta4, backend abort |
Date: | 2017-09-16 03:38:20 |
Message-ID: | 21764.1505533100@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Sat, Sep 16, 2017 at 7:26 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Attached is an updated patch that incorporates the ideas you suggested.
> I was imagining that you would just need to keep a back pointer to the
> last queued event for the same (relation, command), since that's the
> only one you'd ever need to consider cancelling, and then no scanning
> would be needed. I am probably missing something.
There could be more than one after-statement trigger, no?
>> This is pretty messy but I think it's the best we can do as long as
>> RI actions are intermixed with other AFTER ROW triggers.
> It does seem like an inconsistency that it would be good to fix, but I
> don't immediately see how to make that happen with the current design.
> It would be interesting to know what DB2 does here in terms of trigger
> execution contexts and transition tables when you have a chain of 2, 3
> and 4 foreign key referential actions.
> Is it worth adding a test with an extra level of chaining in the self_ref case?
Would it show anything not shown by the three-level case?
> Is it worth adding tests for SET NULL and SET DEFAULT, to exercise the
> complete set of referential actions?
I think they're all about the same as far as this is concerned.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | postgresql_2016@163.com | 2017-09-16 08:06:02 | 】 |
Previous Message | Iain Barnett | 2017-09-16 02:08:28 | PGAdmin 4 OSX app "…is damaged and can’t be opened" |