Re: Identity projection - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Identity projection
Date
Msg-id 8465.1360380793@sss.pgh.pa.us
Whole thread Raw
In response to Re: Identity projection  (Amit kapila <amit.kapila@huawei.com>)
Responses Re: Identity projection
Re: Identity projection
List pgsql-hackers
Amit kapila <amit.kapila@huawei.com> writes:
>> if (!is_projection_capable_plan(result_plan) && compare_tlist_exprs(sub_tlist, result_plan->targetlist) )

> Sorry, the check I suggested in last mail should be as below:

> if (!is_projection_capable_plan(result_plan) && !compare_tlist_exprs(sub_tlist, result_plan->targetlist) )

You know, I was thinking that compare_tlist_exprs() was a pretty
unhelpfully-chosen name for a function returning boolean, and this
thinko pretty much proves the point.  It'd be better to call it
something like equivalent_tlists(), tlists_are_equivalent(), etc.
(I'm not caring for the emphasis on the exprs either, because I think
it'll also be necessary to compare resjunk fields for instance.)
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit kapila
Date:
Subject: Re: Identity projection
Next
From: Tom Lane
Date:
Subject: Re: missing rename support