Re: print_path is missing GatherMerge and CustomScan support

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: print_path is missing GatherMerge and CustomScan support
Date: 2018-07-27 07:02:32
Message-ID: 20180727070232.GK1754@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 27, 2018 at 03:40:48PM +0900, Etsuro Fujita wrote:
> (I think that at least currently, there is no need for the Gather and
> GatherMerge cases in reparameterize_path_by_child, but I don't object to
> keeping those as-is there.)

Let's keep them. As far as my understanding goes, which is way lower
than any of you by the way, those don't hurt and would automatically
help.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Toshi Harada 2018-07-27 07:08:13 Re: "WIP: Data at rest encryption" patch and, 2 phase commit.
Previous Message Etsuro Fujita 2018-07-27 06:40:48 Re: print_path is missing GatherMerge and CustomScan support