Re: slight tweaks to documentation about runtime pruning - Mailing list pgsql-hackers

From Amit Langote
Subject Re: slight tweaks to documentation about runtime pruning
Date
Msg-id 304131bd-e1a5-8cb1-25b6-5b567463fde2@lab.ntt.co.jp
Whole thread Raw
In response to Re: slight tweaks to documentation about runtime pruning  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: slight tweaks to documentation about runtime pruning
List pgsql-hackers
On 2018/12/10 0:57, Amit Langote wrote:
> On Sun, Dec 9, 2018 at 8:13 PM David Rowley
> <david.rowley@2ndquadrant.com> wrote:
>> listp1 was scanned twice (loops=2), listp2 was scanned just once.
>>
>> Now it is true that if the subplan was executed 0 times that it will
>> appear as "(never executed)", but do we really need to explain in this
>> area that "(never executed)" means loops=0?
> 
> Ah, I see what you mean.  So, "(never executed)" is not the only sign
> of of run-time pruning occurring.  The value of loops can be different
> for different subplans / partitions, and it being lower for a given
> subplan means that the subplan has been pruned more number of times.

I updated the patch.  Regarding whether we should mention "(never
executed)", it wouldn't hurt to mention it imho, exactly because it's
shown in the place of showing loops=0.  How about the attached?

Thanks,
Amit

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit
Next
From: Thomas Munro
Date:
Subject: Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit