Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dr7ZM-0005YF-0p for pgsql-bugs@arkaria.postgresql.org; Sun, 10 Sep 2017 19:07:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dr7ZK-0002Ni-VW for pgsql-bugs@arkaria.postgresql.org; Sun, 10 Sep 2017 19:06:59 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dr7ZK-0002NY-8Z for pgsql-bugs@postgresql.org; Sun, 10 Sep 2017 19:06:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dr7ZH-0006TL-Pk; Sun, 10 Sep 2017 19:06:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v8AJ2rRW025327; Sun, 10 Sep 2017 15:02:53 -0400 From: Tom Lane To: Thomas Munro cc: Michael Paquier , phb07@apra.asso.fr, Andrew Gierth , PostgreSQL mailing lists Subject: Re: BUG #14808: V10-beta4, backend abort In-reply-to: <9324.1504983594@sss.pgh.pa.us> References: <20170909064853.25630.12825@wrigleys.postgresql.org> <3702.1504976930@sss.pgh.pa.us> <9324.1504983594@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Sat, 09 Sep 2017 14:59:54 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25325.1505070173.1@sss.pgh.pa.us> Date: Sun, 10 Sep 2017 15:02:53 -0400 Message-ID: <25326.1505070173@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org I wrote: > Now, the ExecEndModifyTable instance for the DELETE supposes that > all TCS-using triggers must have been fired during ExecutorFinish; > but *that doesn't happen if EXEC_FLAG_SKIP_TRIGGERS is set*, which > it is because ri_PerformCheck tells SPI not to fire triggers. In view of the fact that 10rc1 wraps tomorrow, there doesn't seem to be time to do anything better about this than my quick hack. So I went ahead and pushed that, with a regression test case. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs