| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum and Autoanalyze |
| Date: | 2008-09-17 14:22:28 |
| Message-ID: | 20080917142228.GA3855@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs wrote:
>
> On Wed, 2008-09-17 at 10:09 +0300, Heikki Linnakangas wrote:
> > Isn't autoanalyze a waste of time during a bulk load? Seems better to
> > run ANALYZE manually at the end.
>
> Its not a waste of time because it catches tables immediately they have
> been loaded, not just at the end of the bulk load. Running ANALYZE is a
> waste of time if autoanalyze has already caught it, which is why that's
> never been added onto the end of a pg_dump script. But currently this is
> true only when we have both autoVACUUM and autoANALYZE enabled.
Hmm, one of the first complaints about defaulting autovacuum to on was
that it made restores so much longer *because* it was choosing to do
autoanalyzes on the tables as they were imported. It was then that the
auto-cancel mechanism was introduced.
http://pgsql.markmail.org/message/rqyjkafuw43426xy
Why doesn't this new request conflict with that one?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2008-09-17 14:29:23 | Re: [PATCHES] libpq events patch (with sgml docs) |
| Previous Message | Ron Mayer | 2008-09-17 14:19:18 | Re: Patch for SQL-standard negative valued year-month literals |