Re: Planner debug views - Mailing list pgsql-hackers

From Qingqing Zhou
Subject Re: Planner debug views
Date
Msg-id CAJjS0u3VEUawDDGJu0ykfdF7K-PPvsWVwxEBQ7tm7vno35va2A@mail.gmail.com
Whole thread Raw
In response to Re: Planner debug views  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Planner debug views  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Jul 28, 2015 at 12:08 PM, Alvaro Herrera
<alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: Remaining 'needs review' patchs in July commitfest
Next
From: David Rowley
Date:
Subject: Re: WIP: Make timestamptz_out less slow.