Re: print_path is missing GatherMerge and CustomScan support

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: print_path is missing GatherMerge and CustomScan support
Date: 2018-07-19 00:07:22
Message-ID: 20180719000722.GA3411@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 18, 2018 at 12:15:25PM +0530, Ashutosh Bapat wrote:
> Yes that's right. Thanks for taking care of it.

Okay, I have pushed a fix for this one as that's wrong and
back-patched to v11. The coverage of reparameterize_path_by_child is
actually quite poor if you look at the reports:
https://coverage.postgresql.org/src/backend/optimizer/util/pathnode.c.gcov.html

Could it be possible to stress that more? This way mistakes like this
one could have been avoided from the start.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-07-19 00:19:58 Re: untrusted PLs should be GRANTable
Previous Message Tom Lane 2018-07-18 23:25:37 Re: Have an encrypted pgpass file