From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: pg@pmenke.de
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs
Date: Sat, 23 Jan 2021 18:44:11 -0300
Message-ID: <20210123214411.GA12320@alvherre.pgsql> (raw)
In-Reply-To: <16794-350a655580fbb9ae@postgresql.org>
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
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, pg@pmenke.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16794: BEFORE UPDATE FOR EACH ROW triggers on partitioned tables can break tuple moving UPDATEs
In-Reply-To: <20210123214411.GA12320@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