Qingqing Zhou wrote: > On Thu, Jul 30, 2015 at 2:42 PM, Jim Nasby <jim.na...@bluetreble.com> wrote: > > > > I think a better option would be shoving it into a backend tuplestore and > > just leaving it there (maybe with a command to clear it for the paranoid). > > That gives a relation you can query against, insert into another table, etc. > > This is something I don't know how to do it: in my understanding, a > tuplestore is an internal store, which means it has no name exposed. > Thus we can't reference it later.
Yeah, that doesn't sound the kind of project you should attempt here. EXPLAIN already knows to return tuples, so I was assuming you would return your stuff using that mechanism. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
