Re: update/delete and execution-time partition pruning

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: update/delete and execution-time partition pruning
Date: 2021-05-11 03:46:13
Message-ID: CAApHDvqhhQHrLBQdgyC=e3ykdf2rDp4a-KfyAO7MQHG59W-1rg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 11 May 2021 at 15:36, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>
> We apparently forgot in 86dc90056df to remove a note in 5.11.4.
> Partition Pruning saying this:
>
> <note>
> <para>
> Execution-time partition pruning currently only occurs for the
> <literal>Append</literal> and <literal>MergeAppend</literal> node types.
> It is not yet implemented for the <literal>ModifyTable</literal> node
> type, but that is likely to be changed in a future release of
> <productname>PostgreSQL</productname>.
> </para>
> </note>
>
> Now because we include the Append/MergeAppend node even if the query
> is update/delete, this note is no longer useful or valid.
>
> Attached patch removes that note.

Yeah. Agreed. That's out of date now.

I'll take care of this.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2021-05-11 03:53:54 Re: PG 14 release notes, first draft
Previous Message Andrey Lepikhov 2021-05-11 03:45:21 Defer selection of asynchronous subplans until the executor initialization stage