Re: making update/delete of inheritance trees scale better

Amit Langote <amitlangote09@gmail.com>

View thread View on postgr.es

From: Amit Langote <amitlangote09@gmail.com>

To: Heikki Linnakangas <hlinnaka@iki.fi>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2021-03-03T14:39:01Z

Lists: pgsql-hackers

Attachments

v10-0001-Overhaul-how-updates-compute-new-tuple.patch (application/octet-stream) patch v10-0001
v10-0002-Revise-how-inherited-update-delete-are-handled.patch (application/octet-stream) patch v10-0002

Just noticed that a test added by the recent 927f453a941 fails due to
0002.  We no longer allow moving a row into a postgres_fdw partition
if it is among the UPDATE's result relations, whereas previously we
would if the UPDATE on that partition is already finished.

To fix, I've adjusted the test case.  Attached updated version.

-- 
Amit Langote
EDB: http://www.enterprisedb.com

Commits

Rework planning and execution of UPDATE and DELETE.
- 86dc90056dfd 14.0 landed
Faster expression evaluation and targetlist projection.
- b8d7f053c5c2 10.0 cited