pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: a.roland@index.de
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting
Date: Thu, 12 Dec 2019 09:52:29 -0300
Message-ID: <20191212125229.GA8225@alvherre.pgsql> (raw)
In-Reply-To: <16153-dd8a42806bf9cb79@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





view thread (2+ messages)

Message-ID: <20191212125229.GA8225@alvherre.pgsql>
Permalink:  ../20191212125229.GA8225@alvherre.pgsql/
Also on:    postgresql.org/message-id/20191212125229.GA8225@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: alvherre@2ndquadrant.com, a.roland@index.de
  Subject: Re: BUG #16153: foreign key update should probably move dependent rows in the case of tuple rerouting
  In-Reply-To: <20191212125229.GA8225@alvherre.pgsql>
  References: <16153-dd8a42806bf9cb79@postgresql.org> <20191212125229.GA8225@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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