Re: tuple properties out of TupleTableSlot

Поиск
Список
Период
Сортировка
От Schoudel, Brian
Тема Re: tuple properties out of TupleTableSlot
Дата
Msg-id AF1BE4D7F414834EAA1E9672B79484BB2E0F2E@adminmail3.ui.uillinois.edu
обсуждение исходный текст
Ответ на tuple properties out of TupleTableSlot  ("Schoudel, Brian" <BrianS@uillinois.edu>)
Ответы Re: tuple properties out of TupleTableSlot
Список pgsql-hackers
Tom,

Just for testing, I stuffed it into ExecEvalVar under the switch statement in execQual.c.  This was a chosen spot I was
fairlycertain I could get some kind of output. 

TupleTableSlot *slot;
TupleDesc       tuple_type;

The above portion is actually part of the delivered source code.

Maybe I need to as you said wrap a NameStr() around it?

Thanks

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Saturday, December 11, 2004 12:47 PM
To: Schoudel, Brian
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] tuple properties out of TupleTableSlot


"Schoudel, Brian" <BrianS@uillinois.edu> writes:
> I'm a beginning developer to postgresql working on a CS Master's project trying to implement a new join operator.  My
questionis how to effectively break down a TupleTableSlot into it's properties.  I've been messing around with it for
hoursnow and thought the code below would return the attribute name for table but instead just returns some binary
info.

The code looks ok as far as it goes ... it's not using NameStr() which I
would consider good style, but that's just cosmetic.

What context is this being called in, and where are you getting the slot
from?  I think you're probably not really using a valid slot ...
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Mark Cave-Ayland"
Дата:
Сообщение: Re: join selectivity
Следующее
От: "Mark Cave-Ayland"
Дата:
Сообщение: Re: [postgis-devel] RE: join selectivity