From: Tom Lane <tgl@sss.pgh.pa.us>
To: ochedru@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17930: Regression in DISABLE TRIGGER ALL
In-reply-to: <17930-73168e744fdf85c0@postgresql.org>
References: <17930-73168e744fdf85c0@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 12 May 2023 07:52:13 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1315365.1683898740.1@sss.pgh.pa.us>
Date: Fri, 12 May 2023 09:39:00 -0400
Message-ID: <1315366.1683898740@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1315366.1683898740%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The following script creates a partition table with a foreign key and works
> fine on PostgreSQL 14:

> begin;
> create table a(id int primary key);
> create table b(id int primary key, a_id int not null references a(id))
> partition by range(id);
> create table b_default(like b including defaults including constraints);
> alter table b attach partition b_default default;
> alter table b disable trigger all;
> commit;

> On PostgresSQL 15, it fails on DISABLE TRIGGER ALL:
> ERROR:  trigger "RI_ConstraintTrigger_c_20196703" for table "b_default" does
> not exist

It works for me with 15.3.  I don't think you are actually running
15.3 (i.e., yesterday's minor release), because this symptom matches
a bug we fixed in 15.3.

			regards, tom lane