| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Pavan Deolasee <pavan(at)enterprisedb(dot)com>, Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Autovacuum Improvements |
| Date: | 2007-01-16 14:25:25 |
| Message-ID: | 20070116142525.GW24671@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Simon Riggs wrote:
> Perhaps we should focus on the issues that might result, so that we
> address those before we spend time on the details of the user interface.
> Can we deadlock or hang from running multiple autovacuums?
If you were to run multiple autovacuum processes the way they are today,
maybe. But that's not my intention -- the launcher would be the only
one to read the catalogs; the workers would be started only to do a
single VACUUM job. This reduces the risk of this kind of problems.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-01-16 14:29:18 | Re: [HACKERS] Autovacuum Improvements |
| Previous Message | Jasbinder Singh Bali | 2007-01-16 14:24:22 | Re: Dynamic loading of Perl Code in Postgres functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-01-16 14:27:53 | Re: Enabling autovacuum by default (was Re: Autovacuum |
| Previous Message | Alvaro Herrera | 2007-01-16 14:23:36 | Re: Autovacuum improvements |