Re: BUG #17930: Regression in DISABLE TRIGGER ALL
От | Olivier Chédru |
---|---|
Тема | Re: BUG #17930: Regression in DISABLE TRIGGER ALL |
Дата | |
Msg-id | CAC1_XpS5zDhAVObBFTjJqzzhhhX8jk1RMV_C0p7NOc8GZRpp5g@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #17930: Regression in DISABLE TRIGGER ALL (PG Bug reporting form <noreply@postgresql.org>) |
Список | pgsql-bugs |
My bad, this issue is a duplicate of bug #17817 and has been fixed in PostgreSQL 15.3.
Sorry for the spam.
On Fri, May 12, 2023 at 9:53 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:
Bug reference: 17930
Logged by: Olivier Chédru
Email address: ochedru@gmail.com
PostgreSQL version: 15.3
Operating system: Linux
Description:
Hi!
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 seems to use a wrong trigger name. In this case,
RI_ConstraintTrigger_c_20196703 is the name of a trigger defined on the
parent table b.
Thank you.
В списке pgsql-bugs по дате отправления: