Re: [HACKERS] Slow count(*) again... - Mailing list pgsql-performance

From Vitalii Tymchyshyn
Subject Re: [HACKERS] Slow count(*) again...
Date
Msg-id 4D4C0F66.1080507@gmail.com
Whole thread Raw
In response to Re: [HACKERS] Slow count(*) again...  (Kenneth Marshall <ktm@rice.edu>)
Responses Re: [HACKERS] Slow count(*) again...  (Robert Haas <robertmhaas@gmail.com>)
Re: [HACKERS] Slow count(*) again...  (david@lang.hm)
List pgsql-performance
04.02.11 16:33, Kenneth Marshall написав(ла):
>
> In addition, the streaming ANALYZE can provide better statistics at
> any time during the load and it will be complete immediately. As far
> as passing the entire table through the ANALYZE process, a simple
> counter can be used to only send the required samples based on the
> statistics target. Where this would seem to help the most is in
> temporary tables which currently do not work with autovacuum but it
> would streamline their use for more complicated queries that need
> an analyze to perform well.
>
Actually for me the main "con" with streaming analyze is that it adds
significant CPU burden to already not too fast load process. Especially
if it's automatically done for any load operation performed (and I can't
see how it can be enabled on some threshold).
And you can't start after some threshold of data passed by since you may
loose significant information (like minimal values).

Best regards, Vitalii Tymchyshyn

pgsql-performance by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: Talking about optimizer, my long dream
Next
From: Greg Smith
Date:
Subject: Re: Query performance with disabled hashjoin and mergejoin