| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | HOT and autovacuum |
| Date: | 2008-03-03 21:03:48 |
| Message-ID: | 20080303210348.GA7321@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I'm seeing a 8.3 database whose autovacuum-initiated vacuums are being
cancelled and I am not sure of the cause. I am wondering if a HOT
cleanup round on a page could try to acquire locks on it that would
conflict with autovacuum (basically anything that conflicts with a
vacuum lock). This would cause autovacuum to commit hara-kiri.
If the table is frequently updated and HOT is invoked often, this could
be very frequent. The auto-cancel feature of autovacuum is IMHO, in
this case, not welcome. Perhaps we could teach autovac to not cancel
itself if the other locker is a HOT page prune?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-03-03 21:23:30 | libpq type system 0.9a |
| Previous Message | Bruce Momjian | 2008-03-03 20:42:33 | Re: proposal: plpgsql return execute ... |