a misbehavior of partition row movement (?) - Mailing list pgsql-hackers

From David G. Johnston
Subject a misbehavior of partition row movement (?)
Date
Msg-id CAKFQuwYyrHRZDQ_stgEkwiZ7zQXOdY2650o660WZxkKVZDPE+w@mail.gmail.com
Whole thread Raw
In response to a misbehavior of partition row movement (?)  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: a misbehavior of partition row movement (?)
List pgsql-hackers
On Friday, October 2, 2020, Amit Langote <amitlangote09@gmail.com> wrote:

Reporter on that thread says that the last update should have failed
and I don't quite see a workable alternative to that. 
 
To be clear the OP would rather have it just work, the same as the non-row-movement version.  Maybe insert the new row first, execute the on update trigger chained from the old row, then delete the old row?

David J.

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: enable_incremental_sort changes query behavior
Next
From: "Daniel Verite"
Date:
Subject: Re: Rejecting redundant options in Create Collation