Re: Small run-time pruning doc fix

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Small run-time pruning doc fix
Дата
Msg-id 301c3150-f673-6c58-5a85-57956ff9bef7@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: Small run-time pruning doc fix  (David Rowley <david.rowley@2ndquadrant.com>)
Ответы Re: Small run-time pruning doc fix  (David Rowley <david.rowley@2ndquadrant.com>)
Список 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.eisentraut@2ndquadrant.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Continue work on changes to recovery.conf API
Следующее
От: Jürgen Strobel
Дата:
Сообщение: Re: BUG #15212: Default values in partition tables don't work asexpected and allow NOT NULL violation