Re: lifetime of TubleTableSlot* returned by ExecProcNode

From: "Bramandia Ramadhana" <bramandia(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: lifetime of TubleTableSlot* returned by ExecProcNode
Date: 2008-12-13 23:03:19
Message-ID: 700260640812131503hc5b9754w78ff4721f965c4b9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I see. Thanks for the advice. I would research on how to use tuplestore
object.

Regards,

Bramandia R.

On Sat, Dec 13, 2008 at 10:36 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Bramandia Ramadhana" <bramandia(at)gmail(dot)com> writes:
> > Hmm how if an upper level node needs to store (for future use) the
> > TupleTableSlot* returned by lower level node, e.g. I create a specialized
> > Sort Node which needs to read all tuples from lower level nodes. In this
> > case, would it be necessary and sufficient to make a copy the
> TupleTableSlot
>
> It would be a pretty crummy way to approach it, because a Slot is not
> intended to be a compact representation. You probably want to use a
> tuplestore or tuplesort object instead.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Mielke 2008-12-13 23:29:08 Re: Sync Rep: First Thoughts on Code
Previous Message Ned T. Crigler 2008-12-13 22:57:44 visibility map and reltuples