pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting 2+ messages / 2 participants [nested] [flat]
* BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting @ 2019-12-05 16:02 PG Bug reporting form <noreply@postgresql.org> 0 siblings, 1 reply; 2+ messages in thread From: PG Bug reporting form @ 2019-12-05 16:02 UTC (permalink / raw) To: pgsql-bugs@lists.postgresql.org; +Cc: a.roland@index.de 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting @ 2019-12-12 12:52 Alvaro Herrera <alvherre@2ndquadrant.com> parent: PG Bug reporting form <noreply@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Alvaro Herrera @ 2019-12-12 12:52 UTC (permalink / raw) To: a.roland@index.de; pgsql-bugs@lists.postgresql.org On 2019-Dec-05, PG Bug reporting form wrote: > foreign key update should probably move dependent rows in the case of > tuple rerouting > instead of simply deleting them silently Hmm. > 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; This seems to be a side-effect of how tuple updates work across partitions. My bet is that it's seen as just a deletion, which deletes the referencing tuple because of the ON DELETE CASCADE; then the other row is inserted and nothing else needs to happen. You don't have ON UPDATE CASCADE in your example, so my expectation would be that this should raise an error, per NO ACTION. But if you were to add ON UPDATE CASCADE, then yeah the referencing row should be moved too somehow. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2019-12-12 12:52 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2019-12-05 16:02 BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting PG Bug reporting form <noreply@postgresql.org> 2019-12-12 12:52 ` Alvaro Herrera <alvherre@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox