From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | <rafael(at)akyasociados(dot)com(dot)ar> |
Cc: | <mpartio(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Vacum Analyze problem |
Date: | 2007-09-04 23:24:32 |
Message-ID: | 87bqci580f.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
<rafael(at)akyasociados(dot)com(dot)ar> writes:
> I knew that in the long run the VACUUM ANALYZE comand has to be executed
> again. My question is if something can happen over night and cause the need
> of a new VACUUM ANALYZE (regenerating indexes or other thing related with
> performance).
The answer to your question is possibly yes for two reasons:
1) If you're running an autovacuum daemon it might decide it's time to vacuum
the table and kick off a vacuum. That sounds most like what you're describing.
2) If the size of the table changes substantially becoming much larger (or
smaller but that wouldn't happen just due to deletes unless you run vacuum)
then recent versions of Postgres will notice even if you don't run analyze and
take that into account.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Rubio | 2007-09-05 07:31:05 | No pg_dumplo on 8.2.4 |
Previous Message | Scott Marlowe | 2007-09-04 23:15:16 | Re: Performance on 8CPU's and 32GB of RAM |