| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Galy Lee <lee(dot)galy(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Restartable VACUUM design overview version 2 |
| Date: | 2007-03-06 03:25:25 |
| Message-ID: | 69408AB9-28E5-4C25-AE90-DC6A131C265C@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 5, 2007, at 2:48 AM, Galy Lee wrote:
> (2) interrupt VACUUM when it is running.
> Another approach is to interrupt the running VACUUM. VACUUM checks
> for a smart stop request at normal vacuum delay points, if such a
> request is detected, a flag is set to tell VACUUM to stop at a
> right
> point. VACUUM stops at the end of one full fill-workmem-clean-index
> -clean-deadtuple cycle.
What about 2a: when an interrupt is requested, if the heap scan i sin
progress stop it immediately and proceed to index cleanup, rather
than waiting for maintenance_work_mem to fill.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2007-03-06 03:34:35 | Re: Log levels for checkpoint/bgwriter monitoring |
| Previous Message | Jim Nasby | 2007-03-06 03:04:46 | Re: PostgreSQL - 'SKYLINE OF' clause added! |