| From: | Chris <csmith(at)squiz(dot)net> |
|---|---|
| To: | gerry(dot)smit(at)lombard(dot)ca |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Answering my own question |
| Date: | 2002-05-15 23:28:33 |
| Message-ID: | 5.1.0.14.0.20020516092500.00a9ea70@cooee.cybersydney.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
>Now THAT's REALLY fascinating. We upgraded from 6.5 to 7.1 about 4-5
>months ago , and only got this problem after that. I leave "ANALYZE" out of
>VACUUM due to the large volume of (I though needless) output that gets
>piped to my cron_log.
>
>Does anyone have a feal for how "necessary" VACUUM ANALYZE is over "VACUUM"
>??
As you noticed, pretty necessary :)
A vacuum analyze updates the statistics used when the planner decides on
what action to take (whether it's a sequential scan, using an index etc).
A plain vacuum removes dead tuples from the system, not much else.
-----------------
Chris Smith
http://www.squiz.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-05-16 00:14:58 | Re: data-type for image files |
| Previous Message | Balazs Wellisch | 2002-05-15 22:57:37 | Re: Answering my own question |