Marko Kreen escribió:
> On 8/29/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Alvaro Herrera <alvherre@commandprompt.com> writes:
> > > I'm not having much luck really. I think the problem is that ANALYZE
> > > stores reltuples as the number of live tuples, so if you delete a big
> > > portion of a big table, then ANALYZE and then VACUUM, there's a huge
> > > misestimation and extra index cleanup passes happen, which is a bad
> > > thing.
> >
> > Yeah ... so just go with a constant estimate of say 200 deletable tuples
> > per page?
>
> Note that it's much better to err on the smaller values.
>
> Extra index pass is really no problem.
Humm, is it? If you have a really big table (say, a hundred million
tuples) and two indexes then you are not happy when vacuum must make two
passes over the indexes. It may mean vacuum taking five hours instead
of three with vacuum delay. Remember, you must scan each index
*completely* each time.
> VACUUM getting "Out of memory" may not sound like a big problem, but
> the scary thing is - the last VACUUM's memory request may succeed and
> that means following queries start failing and that is big problem.
Maybe what we should do is spill the TID list to disk instead. TODO for
8.4?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
