2009/12/16 decibel
> On Dec 11, 2009, at 8:44 PM, Tom Lane wrote:
> > Bruce Momjian writes:
> >> Ashish 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 specifie
On Dec 11, 2009, at 8:44 PM, Tom Lane wrote:
> Bruce Momjian writes:
>> Ashish 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 even have a
Tom Lane escreveu:
> I'm not sure there is any really nice solution within the confines of
> plain ASCII text output. There was an interesting approach online
> at http://explain-analyze.info, but that site seems to be down now :-(
>
Estimation error is one of the ideas. The other ones I have in
Bruce Momjian writes:
> Ashish 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 even have a sample patch you can use as a start, attached.
Of co
Robert Haas wrote:
> On Fri, Dec 11, 2009 at 9:05 PM, Bruce Momjian wrote:
> > Ashish 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.
> >>
On Fri, Dec 11, 2009 at 9:05 PM, Bruce Momjian wrote:
> Ashish 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 s
On Fri, Dec 11, 2009 at 9:00 PM, Ashish 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 proc
Ashish 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
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
Peter Eisentraut wrote:
But unless the item is linked to a mailing
list thread that already shows a consensus about the feature, you need
to start with a discussion about a plan.
And realistically, even if the item is so linked, someone new to the
project still shouldn't just plow away on it
On mån, 2009-12-07 at 09:53 +0100, Albe Laurenz wrote:
> I would start with the TODO list: http://wiki.postgresql.org/wiki/Todo
> These are things for which there is a consensus that it would be
> a good idea to implement them.
The Todo list is not a list of things for which such a consensus exist
On Mon, Dec 7, 2009 at 8:04 PM, Ashish wrote:
> Hi Robert,
>
> Thanks. If I may, what encompasses your area of expertise...
>
> BTW Congratulation on becoming a committer!
Thanks. As others have said, it's probably best to pick a project
first, or at least an area. It's more important to find s
Hi Robert,
Thanks. If I may, what encompasses your area of expertise...
BTW Congratulation on becoming a committer!
Regards
Ashish
On Mon, 7 Dec 2009, Robert Haas wrote:
On Sun, Dec 6, 2009 at 9:24 PM, wrote:
2. Would someone be willing to be a mentor? It would be nice to be able to get
On 12/7/09 4:41 PM, Ashish wrote:
> Albe & Joshua, thanks for the advice. I am in the process of deciding
> what to work on and am looking at the TODO list. I definitely do not
> intend to work in a vacuum :-) I am really excited about this and look
> forward to being challenged and learning a lot.
Albe & Joshua, thanks for the advice. I am in the process of deciding what to
work on and am looking at the TODO list. I definitely do not intend to work in a
vacuum :-) I am really excited about this and look forward to being challenged and
learning a lot.
Regards
Ashish
On Mon, 7 Dec 2009,
On Sun, Dec 6, 2009 at 9:24 PM, wrote:
> 2. Would someone be willing to be a mentor? It would be nice to be able to
> get some guidance on a one-to-one basis.
I might be willing to do this, but if you pick a project that is
outside my area of knowledge then I might not be able to help as much.
On Mon, Dec 07, 2009 at 09:53:32AM +0100, Albe Laurenz wrote:
> abindra wrote:
> > Next quarter I am planning to do an Independent Study course
> > where the main objective would be to allow me to get familiar
> > with the internals of Postgres by working on a project(s). I
> > would like to wor
abindra wrote:
> Next quarter I am planning to do an Independent Study course
> where the main objective would be to allow me to get familiar
> with the internals of Postgres by working on a project(s). I
> would like to work on something that could possibly be
> accepted as a patch.
>
> This
Hello there,
I am a graduate student at the University of Washington, Tacoma
(http://www.tacoma.washington.edu/tech/) with an interest in databases
(especially query processing). I am familiar with database theory and in an
earlier life I used to be an application developer and have done a lot o
19 matches
Mail list logo
