Re: making update/delete of inheritance trees scale better

Amit Langote <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-02-16T13:42:57Z
Lists: pgsql-hackers

Attachments

On Thu, Feb 4, 2021 at 3:22 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Tue, Jan 26, 2021 at 8:54 PM Amit Langote <amitlangote09@gmail.com> wrote:
> > 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.
>
> Broken again, so rebased.

Rebased.

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

Commits

  1. Rework planning and execution of UPDATE and DELETE.

  2. Faster expression evaluation and targetlist projection.