From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
---|---|
To: | |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | [pgAdmin III] #132: Use one of the new format for the graphical EXPLAIN |
Date: | 2010-01-26 09:19:52 |
Message-ID: | 045.021ea12a1b815ca7c58a2bf9b6407ae6@code.pgadmin.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
#132: Use one of the new format for the graphical EXPLAIN
-----------------------+----------------------------------------------------
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: querytool | Platform: all
-----------------------+----------------------------------------------------
Quote from Magnus:
> Right. What I'd envision us doing is a simple
> if (version < 9.0)
> run_old_explain_code();
> else
> run_new_explain_code();
>
> and only the codepath for run_new_explain_code() - which would use a
> machine format output - would have the implementation of any of these
> new parameters.
>
> It would be slightly more work to get started since the new parser
> needs to be done (hopefully there are classes that'll do 95% of that
> for us already though), but not having to maintain manual parsing of
> these new options should be a win in the long run.
>
> And eventually, some 5 years from now or so, we can retire the old
> explain code because we no longer support pre-9.0 versions :D
>
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/132>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
From | Date | Subject | |
---|---|---|---|
Next Message | pgAdmin Trac | 2010-01-26 22:06:22 | [pgAdmin III] #133: Column's distinct options have a new syntax |
Previous Message | Guillaume Lelarge | 2010-01-26 09:18:14 | Re: Ticket 117: Explain Buffers |