From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
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-18 18:13:56 |
Message-ID: | CA+TgmoZD3=Khv1BrLPYDNc3btq4=go-RyXzhETBHw4gZLDjiRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-04-18 18:21:50 | Re: block-level incremental backup |
Previous Message | Robert Haas | 2019-04-18 18:05:40 | Re: block-level incremental backup |