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-01-26T11:54:09Z

Lists: pgsql-hackers

Attachments

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

On Fri, Nov 13, 2020 at 6:52 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Wed, Nov 11, 2020 at 9:11 PM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> > On 29/10/2020 15:03, Amit Langote wrote:
> > > Rebased over the recent executor result relation related commits.
> >
> > ModifyTablePath didn't get the memo that a ModifyTable can only have one
> > subpath after these patches. Attached patch, on top of your v5 patches,
> > cleans that up.
>
> Ah, thought I'd taken care of that, thanks.  Attached v6.

This got slightly broken due to the recent batch insert related
changes, so here is the rebased version.  I also made a few cosmetic
changes.

-- 
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