From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Small run-time pruning doc fix |
Date: | 2018-11-12 13:46:07 |
Message-ID: | 301c3150-f673-6c58-5a85-57956ff9bef7@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/11/2018 06:23, David Rowley wrote:
> Thanks for looking at this.
>
> On 2 November 2018 at 20:30, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> <para>
>> - Execution-time partition pruning currently occurs for the
>> + 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.
>> </para>
>>
>> Isn't this implied by the preceding paragraph
>>
>> Currently, pruning of partitions during the planning of an UPDATE or
>> DELETE command is implemented using the constraint exclusion method
>
> That paragraph is talking about plan-time partition pruning. The
> paragraph the patch changes is mentioning execution-time partition
> pruning. In PG11 we have plan-time partition pruning for Append and
> MergeAppend. UPDATE/DELETE does pruning, but it uses the constraint
> exclusion code which does not work for HASH partitioned tables. In
> PG11 we only have run-time partition pruning for Append. MergeAppend
> support was only added in 5220bb7533 (PG12).
I see now. The actual documentation change was separate in db72302b0a8.
Committed your change.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jürgen Strobel | 2018-11-12 13:52:11 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
Previous Message | Peter Eisentraut | 2018-11-12 13:17:15 | Re: Continue work on changes to recovery.conf API |