| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First steps with 8.3 and autovacuum launcher |
| Date: | 2007-10-04 09:01:41 |
| Message-ID: | 4704ABF5.80500@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> I came up with the following patch. What this does is cancel any
> ANALYZE started by autovacuum, at the top of ALTER TABLE.
There's a small race condition, autoanalyze could start between the
calls autovac_cancel_analyze and relation_open.
And it doesn't solve the problem for autovacuum. Or other commands than
ALTER TABLE, like CLUSTER.
> There is a new function relation_openrv_cav(). This is the same as
> relation_openrv, except that it will also cancel analyzes. I'm still
> wondering if I should merge the two and have a third boolean argument to
> specify whether to do the cancel.
I like it better the way you have it now.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Smet | 2007-10-04 12:53:16 | Re: First steps with 8.3 and autovacuum launcher |
| Previous Message | Michael Meskes | 2007-10-04 07:59:18 | Re: Not *quite* there on ecpg fixes |