Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pj0SS-0001n1-Vh for pgsql-bugs@arkaria.postgresql.org; Sun, 02 Apr 2023 16:21:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pj0RT-0007zX-F9 for pgsql-bugs@arkaria.postgresql.org; Sun, 02 Apr 2023 16:20:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pj0RT-0007zO-6n for pgsql-bugs@lists.postgresql.org; Sun, 02 Apr 2023 16:20:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pj0RQ-000TVf-NM for pgsql-bugs@lists.postgresql.org; Sun, 02 Apr 2023 16:20:30 +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 332GKQ4A980718; Sun, 2 Apr 2023 12:20:26 -0400 From: Tom Lane To: quynh.helendinh@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17882: I can't disable triggers on a table that has been partitioned In-reply-to: <17882-707c9c1553485c97@postgresql.org> References: <17882-707c9c1553485c97@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Sun, 02 Apr 2023 15:28:37 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <980716.1680452426.1@sss.pgh.pa.us> Date: Sun, 02 Apr 2023 12:20:26 -0400 Message-ID: <980717.1680452426@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > When I try to disable triggers on the table users using this command: > alter table users disable trigger all; > I'm met with this error: > ERROR: trigger "RI_ConstraintTrigger_c_572918" for table "users_0" does not > exist Hi, this was fixed about a month ago (commit f61e60102). That will appear in 15.3, due out in May. regards, tom lane