From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
Cc: | Darcy Buskermolen <darcyb(at)commandprompt(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, 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: [HACKERS] Autovacuum Improvements |
Date: | 2007-01-21 11:39:45 |
Message-ID: | 45B35101.1020108@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Russell Smith wrote:
> Strange idea that I haven't researched, Given Vacuum can't be run in a
> transaction, it is possible at a certain point to quit the current
> transaction and start another one. There has been much chat and now a
> TODO item about allowing multiple vacuums to not starve small tables.
> But if a big table has a long running vacuum the vacuum of the small
> table won't be effective anyway will it? If vacuum of a big table was
> done in multiple transactions you could reduce the effect of long
> running vacuum. I'm not sure how this effects the rest of the system
> thought.
That was fixed by Hannu Krosing's patch in 8.2 that made vacuum to
ignore other vacuums in the oldest xmin calculation.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-21 12:24:38 | Re: [HACKERS] Autovacuum Improvements |
Previous Message | Nicolas Barbier | 2007-01-21 10:22:45 | Re: Installing Postegres side-by-side with M$ SQL server |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-21 12:24:38 | Re: [HACKERS] Autovacuum Improvements |
Previous Message | Martijn van Oosterhout | 2007-01-21 11:17:31 | Re: Simplifying pg_am representation of index sortability |