| From: | Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Planner debug views |
| Date: | 2015-07-28 21:04:50 |
| Message-ID: | CAJjS0u3VEUawDDGJu0ykfdF7K-PPvsWVwxEBQ7tm7vno35va2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 28, 2015 at 12:08 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> I would have a tuplestore, and the planner code would push tuples to it.
> After the planning is done, EXPLAIN can read and return tuples from the
> store to the user.
>
Not sure if I got it: so EXPLAIN will return tuples to libpq client. But
how do we store these returned tuples (RelOptInfo, Path etc) so we can
throw queries against them later?
Something like this:
INSERT INTO my_space SELECT (EXPLAIN SELECT ...); -- won't get parsed
Regards,
Qingqing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2015-07-28 21:37:26 | Re: WIP: Make timestamptz_out less slow. |
| Previous Message | Joe Conway | 2015-07-28 20:56:10 | Re: Remaining 'needs review' patchs in July commitfest |