Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHlMB-00AbjU-JD for pgsql-general@arkaria.postgresql.org; Thu, 13 Jun 2024 14:23:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sHlM8-0025gW-S0 for pgsql-general@arkaria.postgresql.org; Thu, 13 Jun 2024 14:23:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHlM8-0025gN-Gx for pgsql-general@lists.postgresql.org; Thu, 13 Jun 2024 14:23:13 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHlM6-001Tq8-SK for pgsql-general@lists.postgresql.org; Thu, 13 Jun 2024 14:23:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 45DEN7gZ1792893; Thu, 13 Jun 2024 10:23:07 -0400 From: Tom Lane To: David Barbour cc: pgsql-general@lists.postgresql.org Subject: Re: Syntax on BEFORE Trigger - Cascade? In-reply-to: References: Comments: In-reply-to David Barbour message dated "Thu, 13 Jun 2024 09:11:01 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1792891.1718288587.1@sss.pgh.pa.us> Date: Thu, 13 Jun 2024 10:23:07 -0400 Message-ID: <1792892.1718288587@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Barbour writes: > The files are appropriately deleted in Oracle, but Postgres is returning > the following: > *ERROR: Attempt to suppress referential action with before trigger. > CONTEXT: SQL statement "DELETE FROM ONLY "idev"."import_file" WHERE $1 > OPERATOR(pg_catalog.=) "import_job_oid"" * I don't know what you're running there, but there is no such error message in community Postgres. Having said that, maybe what you need is to *not* have any before trigger applied to the import_file table. regards, tom lane