Re: vacuum analyze again...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Jean-Christophe Boggio <cat(at)thefreecat(dot)org>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: vacuum analyze again...
Date: 2001-02-20 19:26:07
Message-ID: 200102201926.OAA14918@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> I find it hard to believe that VAC ANALYZE is all that much slower than
> >> plain VACUUM anyway; fixing the indexes is the slowest part of VACUUM in
> >> my experience. It would be useful to know exactly what the columns are
> >> in a table where VAC ANALYZE is considered unusably slow.
>
> > VACUUM ANALYZE does a huge number of adt/ function calls. It must be
> > those calls that make ANALYZE slower. People report ANALYZE is
> > certainly slower, and that is the only difference.
>
> That's why I'm asking what the data is. The function calls per se can't
> be that slow; I think there must be some datatype-specific issue.
>
> With TOAST in the mix, TOAST fetches could very well be an issue, but
> I didn't think 7.1 was being discussed ...
>

I would love to hear what the issue is with ANALYZE. There isn't much
going on with ANALYZE except the function calls.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adam Haberlach 2001-02-20 19:38:25 user meta (to the database, at least) information
Previous Message Joseph 2001-02-20 19:19:34 RE: postgres load