Re: print_path is missing GatherMerge and CustomScan support - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: print_path is missing GatherMerge and CustomScan support
Date
Msg-id 20180719000722.GA3411@paquier.xyz
Whole thread Raw
In response to Re: print_path is missing GatherMerge and CustomScan support  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Responses Re: print_path is missing GatherMerge and CustomScan support  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List 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

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Have an encrypted pgpass file
Next
From: Stephen Frost
Date:
Subject: Re: untrusted PLs should be GRANTable