Re: tuple properties out of TupleTableSlot - Mailing list pgsql-hackers

From Schoudel, Brian
Subject Re: tuple properties out of TupleTableSlot
Date
Msg-id AF1BE4D7F414834EAA1E9672B79484BB2E0F2E@adminmail3.ui.uillinois.edu
Whole thread Raw
In response to tuple properties out of TupleTableSlot  ("Schoudel, Brian" <BrianS@uillinois.edu>)
Responses Re: tuple properties out of TupleTableSlot
List 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 by date:

Previous
From: "Mark Cave-Ayland"
Date:
Subject: Re: join selectivity
Next
From: "Mark Cave-Ayland"
Date:
Subject: Re: [postgis-devel] RE: join selectivity