Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pg(at)pmenke(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs
Date: 2021-01-23 21:44:11
Message-ID: 20210123214411.GA12320@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2020-Dec-28, PG Bug reporting form wrote:

> i was testing the PG13 enhancement that should allow BEFORE ROW triggers on
> partitioned tables, as long as they don't move the tuple to a different
> partition (original thread:
> https://postgr.es/m/20200227165158.GA2071@alvherre.pgsql). The actual
> restriction on "not to move the tuple to a different partition" seems to be
> a bit stronger though, as the trigger fails, even though not itself, but the
> overarching UPDATE command, did move the tuple.

Hi Philipp, thanks for reporting this issue. Yeah, that should
definitely work. I'll have a look at this in a couple of days and try
my best to have a fix for the February minors.

Regards

--
Álvaro Herrera Valdivia, Chile

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2021-01-24 02:27:43 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Previous Message Ricardo Ungureanu 2021-01-23 15:42:54 Re: BUG #16827: macOS interrupted syscall leads to a crash