Horton

Re: 'update returning *' returns 0 columns instead of empty row with 2 columns when (i) no rows updated and (ii) when applied to a partitioned table with sub-partition

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Petr Fedorov <petr.fedorov@phystech.edu>, pgsql-bugs@postgresql.org
Date: 2019-02-22T04:43:13Z
Lists: pgsql-bugs 
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> Also, I noticed regression test failure having to do with statement
> triggers not firing, which makes sense, as there's no ModifyTable to
> invoke them.

Oh!  You are right, that's a separate bug.  So really we can't have
this fast-path exit at all, we should produce a ModifyTable node in
every case.

I'm too tired to work on that anymore today, do you want to run
with it?

			regards, tom lane

Commits

  1. Fix plan created for inherited UPDATE/DELETE with all tables excluded.