From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | a(dot)roland(at)index(dot)de |
Subject: | BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting |
Date: | 2019-12-05 16:02:33 |
Message-ID: | 16153-dd8a42806bf9cb79@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: 16153
Logged by: Arne Roland
Email address: a(dot)roland(at)index(dot)de
PostgreSQL version: 12.1
Operating system: debian
Description:
--instead of simply deleting them silently
create table a (id serial, primary key (id)) partition by range (id);
create table b (id serial, primary key (id)) partition by range (id);
alter table b add constraint a_fk foreign key (id) references a (id) on
delete cascade;
create table a1 partition of a for values from (1) to (2);
create table a2 partition of a for values from (2) to (3);
create table b1 partition of b for values from (1) to (2);
create table b2 partition of b for values from (2) to (3);
insert into a (id) values (1);
insert into b (id) values (1);
update a set id=2;
select * from b;
Regards
Arne
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2019-12-05 16:52:06 | Re: BUG #16148: Query on Large table hangs in ETL flows and gives out of memory when run in pgAdmin4 |
Previous Message | Tom Lane | 2019-12-05 15:18:10 | Re: BUG #16150: UPDATE set NULL value in non-null columns |