From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Planner debug views |
Date: | 2015-08-03 16:00:43 |
Message-ID: | 20150803160043.GI2441@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Qingqing Zhou wrote:
> On Thu, Jul 30, 2015 at 2:42 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Geoff Winkless | 2015-08-03 16:04:44 | Re: ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types |
Previous Message | Geoff Winkless | 2015-08-03 15:53:08 | ON CONFLICT DO UPDATE using EXCLUDED.column gives an error about mismatched types |