Date: Sat, 23 Jan 2021 18:44:11 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: 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
Message-ID: <20210123214411.GA12320@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <16794-350a655580fbb9ae@postgresql.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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