BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting
Date
Msg-id 16153-dd8a42806bf9cb79@postgresql.org
Whole thread Raw
Responses Re: BUG #16153: foreign key update should probably move dependentrows in the case of tuple rerouting  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      16153
Logged by:          Arne Roland
Email address:      a.roland@index.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


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16150: UPDATE set NULL value in non-null columns
Next
From: Jeff Janes
Date:
Subject: Re: BUG #16148: Query on Large table hangs in ETL flows and gives outof memory when run in pgAdmin4