a misbehavior of partition row movement (?)

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: a misbehavior of partition row movement (?)
Date: 2020-10-02 14:32:56
Message-ID: CAKFQuwYyrHRZDQ_stgEkwiZ7zQXOdY2650o660WZxkKVZDPE+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Friday, October 2, 2020, Amit Langote <amitlangote09(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Verite 2020-10-02 14:37:03 Re: Rejecting redundant options in Create Collation
Previous Message Tomas Vondra 2020-10-02 14:32:07 Re: enable_incremental_sort changes query behavior