Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
Date
Msg-id 54B0784E.6040803@BlueTreble.com
Whole thread Raw
In response to Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
List pgsql-hackers
On 1/9/15, 6:44 PM, Petr Jelinek wrote:
>>>
>> Yep, I had a same impression when I looked at the code first time,
>> however, it is defined as below. Not a manner of custom-scan itself.
>>
>> /*
>>   * ==========
>>   * Scan nodes
>>   * ==========
>>   */
>> typedef struct Scan
>> {
>>      Plan        plan;
>>      Index       scanrelid;      /* relid is index into the range table */
>> } Scan;
>>
>
> Yeah there are actually several places in the code where "relid" means index in range table and not oid of relation,
itstill manages to confuse me. Nothing this patch can do about that.
 

Well, since it's confused 3 of us now... should we change it (as a separate patch)? I'm willing to do that work but
don'twant to waste time if it'll just be rejected.
 

Any other examples of this I should fix too?
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: max_connections documentation
Next
From: Jim Nasby
Date:
Subject: Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)