Re: vacuum analyze again... - Mailing list pgsql-general

From Pete Forman
Subject Re: vacuum analyze again...
Date
Msg-id 14995.33318.905195.486936@kryten.bedford.waii.com
Whole thread Raw
In response to Re: vacuum analyze again...  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: vacuum analyze again...
List pgsql-general
Bruce Momjian writes:
 > > Bruce Momjian <pgman@candle.pha.pa.us> writes:
 > >
 > > > No, we have no ability to randomly pick rows to use for
 > > > estimating statistics.  Should we have this ability?
 > >
 > > That would be really slick, especially given the fact that VACUUM
 > > runs much faster than VACUUM ANALYZE for a lot of PG users.  I
 > > could change my daily maintenance scripts to do a VACUUM of
 > > everything, followed by a VACUUM ANALYZE of the small tables,
 > > followed by a VACUUM ANALYZE ESTIMATE (or whatever) of the large
 > > tables.
 > >
 > > Even cooler would be the ability to set a table size threshold,
 > > so that VACUUM ANALYZE would automatically choose the appropriate
 > > method based on the table size.
 >
 > Added to TODO:
 >
 >         * Allow ANALYZE to process a certain random precentage of
 >           rows

Does this reduced analysis need to be random?  Why not allow the DBA
to specify what rows or blocks to do in some way.
--
Pete Forman                 -./\.- Disclaimer: This post is originated
WesternGeco                   -./\.-  by myself and does not represent
pete.forman@westerngeco.com     -./\.-  opinion of Schlumberger, Baker
http://www.crosswinds.net/~petef  -./\.-  Hughes or their divisions.

pgsql-general by date:

Previous
From: Denis Perchine
Date:
Subject: Re: postgres load
Next
From: Renaud Tthonnart
Date:
Subject: sequence and stored procedure