From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ashish <abindra(at)u(dot)washington(dot)edu> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Joshua Tolley <eggyknap(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Need a mentor, and a project. |
Date: | 2009-12-12 02:28:28 |
Message-ID: | 603c8f070912111828h4f442175ub36d41d135d18125@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Dec 11, 2009 at 9:00 PM, Ashish <abindra(at)u(dot)washington(dot)edu> wrote:
> I am thinking about starting with the following TODO item:
>
> --> Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and actual
> row counts differ by a specified percentage.
>
> I picked this because it is somewhat related to query processing which is
> what I am most interested in. It also <seems> like a good start up project
> for a newbie like me. Before I start looking into what this would involve
> and start a conversation on designing a solution - I wanted to know what you
> guys think about this particular TODO, and it suitability to a newbie.
> Looking forward to your comments...
If we're going to do this, I think we should implement this as an
optional behavior controlled by a new EXPLAIN option (maybe VARIANCE,
following Bruce's patch?) and generate the output using
ExplainProperty<some-data-type>. We could possibly make the option
take an optional threshold indicating how much variance is required
before the variance gets displayed, and display the variance for every
node if VARIANCE is specified without an argument.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-12-12 02:30:20 | Re: Need a mentor, and a project. |
Previous Message | Tom Lane | 2009-12-12 02:27:00 | Re: [PATCH] dtrace probes for memory manager |