From: | Tom Raney <raneyt(at)cecs(dot)pdx(dot)edu> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Planner question |
Date: | 2008-08-12 23:53:50 |
Message-ID: | 48A2228E.3030901@cecs.pdx.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I've been working on a client application (based on the Red Hat Visual
Explain tool) to display all plans the planner considers graphically and
it does that. But, the trace functionality in the planner is always on
(and thus, taking up cycles and resources) whether or not it is
requested by the user.
My question is: How would I let the planner know when a planner session
has been invoked by the "explain" command? If I can slip a flag into
PlannerInfo or PlannerGlobal, that would be perfect. But, I'm a bit
stuck on how to get explain context to that point. I don't want to
modify the planner() entry function parameter list, unless absolutely
necessary.
I currently compile with DEBUG_OPTIMIZER - and that is one option - to
conditionally compile this functionality, but it would be great if this
could run on a lean production system.
-Tom Raney
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2008-08-13 00:38:56 | Re: Uncopied parameters on CREATE TABLE LIKE |
Previous Message | Decibel! | 2008-08-12 23:23:53 | Re: temporary statistics option at initdb time |