From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | ahodgson(at)simkin(dot)ca |
Subject: | BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails |
Date: | 2023-03-01 19:21:44 |
Message-ID: | 17817-31dfb7c2100d9f3d@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17817
Logged by: Alan Hodgson
Email address: ahodgson(at)simkin(dot)ca
PostgreSQL version: 15.2
Operating system: linux-amd64
Description:
This works on 14.7. It fails on 15.2. The Ruby on Rails test suites use
DISABLE TRIGGER ALL extensively.
BEGIN;
CREATE TABLE test_fk (id serial primary key);
CREATE TABLE test_table (test serial, created_at timestamp not null, fk_id
int not null references test_fk(id)) PARTITION BY RANGE (created_at);
CREATE TABLE test_table_2017 PARTITION OF test_table FOR VALUES FROM
('2017-01-01') TO ('2018-01-01');
ALTER TABLE test_table DISABLE TRIGGER ALL;
ROLLBACK;
ERROR: trigger "RI_ConstraintTrigger_c_46838897" for table
"test_table_2017" does not exist
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-03-01 20:51:58 | Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails |
Previous Message | David G. Johnston | 2023-03-01 16:35:29 | Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set |