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

Поиск
Список
Период
Сортировка
От Jim Nasby
Тема Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)
Дата
Msg-id 54B0784E.6040803@BlueTreble.com
обсуждение исходный текст
Ответ на Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)  (Petr Jelinek <petr@2ndquadrant.com>)
Ответы Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список 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 по дате отправления:

Предыдущее
От: Jim Nasby
Дата:
Сообщение: max_connections documentation
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API)