Am Sonntag, den 04.12.2005, 14:02 +0100 schrieb Guido Neitzer:
> On 02.12.2005, at 20:02 Uhr, Jaime Casanova wrote:
>
> > so the way to do it is create a trigger that record in a table the
> > number of rows...
>
> As there are SO MANY questions about the "count(*)" issue, I wonder
> whether it makes sense to add a mechanism which does exactly the
> method mentioned above in a default PostgreSQL installation (perhaps
> switched of by default for other performance impacts)?!
I dont think this would match postgres style - to include
a kludge for a rarely usefull special case. I may be wrong
but personally I never needed unqualified count(*) on a
table to be very fast.
Doing something to enable aggregates in general to use
an existent index would be a nice ide imho.
(With all the visibility hinting in place)
Just my 0.02Ct.
++Tino
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
