| From: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Analyze and vacuum, they are sort of mandatory.... |
| Date: | 2006-02-12 15:05:43 |
| Message-ID: | 18470.24.91.171.78.1139756743.squirrel@mail.mohawksoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Mark Woodward wrote:
>> My question was based on an observation that ANALYZE and VACUUM are
>> nessisary, both for different reasons. The system or tools must be
>> able to detect substantial changes in the database and at least run
>> analyze if failing to do so would cause PostgreSQL to fail badly.
>
> Yes, that is what autovacuum does. It detects changes in the database
> and runs analyze if failing to do so would cause PostgreSQL to behave
> badly. I don't know why it's not turned on by default. You could
> argue about that. But I don't know what else you are looking for.
If that is the answer, then I agree with you, it should be on by default.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-02-12 15:18:23 | Re: SpeedComparison |
| Previous Message | Peter Eisentraut | 2006-02-12 13:57:32 | Re: Analyze and vacuum, they are sort of mandatory.... |