Re: estimated_count() implementation - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: estimated_count() implementation
Date
Msg-id 1161528700.4211.43.camel@silverbirch.site
Whole thread Raw
In response to Re: estimated_count() implementation  (Volkan YAZICI <yazicivo@ttnet.net.tr>)
Responses Re: estimated_count() implementation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, 2006-10-22 at 12:07 +0300, Volkan YAZICI wrote:
> On Oct 21 05:09, Michael Fuhr wrote:
> > I hadn't noticed the TODO item but about a year ago I posted a
> > cursor_plan_rows() function and asked for comments.
> 
> Ah! I didn't see this.
> 
> > The only reply was from Tom, who said, "Given how far off it
> > frequently is, I can't believe that any of the people who ask for the
> > feature would find this a satisfactory answer :-("
> 
> AFAIU, cursor_plan_rows() has some serious limitations like requiring to
> be executed for a portal. I was planning to make estimated_count() work
> for nodeAgg and custom calls too - as count() does.
> 
> But OTOH, Tom's complaints look like still applicable for my
> estimated_count() too. Does this TODO need a little bit more
> clarification or we can count is a redundant one?

http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php

Is the source of the TODO item, though please read the upthread messages
as to how we got there...

I think it would be a useful function...

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: "Gurjeet Singh"
Date:
Subject: Re: New CRC algorithm: Slicing by 8
Next
From: Martijn van Oosterhout
Date:
Subject: Re: New CRC algorithm: Slicing by 8