Re: Runtime pruning problem

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Yuzuko Hosoya <hosoya(dot)yuzuko(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Runtime pruning problem
Date: 2019-04-19 08:03:07
Message-ID: 7d85bc34-3d53-d0ca-8963-7d23debe005e@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019/04/19 3:13, Robert Haas wrote:
> On Tue, Apr 16, 2019 at 10:49 PM Amit Langote
> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> Maybe, not show them? That may be a bit inconsistent, because the point
>> of VERBOSE is to the targetlist among other things, but maybe the users
>> wouldn't mind not seeing it on such empty Append nodes. OTOH, they are
>> more likely to think seeing a subplan that's clearly prunable as a bug of
>> the pruning logic.
>
> Or maybe we could show them, but the Append could also be flagged in
> some way that indicates that its child is only a dummy.
>
> Everything Pruned: Yes
>
> Or something.

Such an approach has been proposed too, although not with a new property text.

Thanks,
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-04-19 08:13:43 Re: Runtime pruning problem
Previous Message Amit Langote 2019-04-19 08:00:57 Re: Runtime pruning problem