Re: Restartable VACUUM design overview version 2 - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Restartable VACUUM design overview version 2
Date
Msg-id 69408AB9-28E5-4C25-AE90-DC6A131C265C@decibel.org
Whole thread Raw
In response to Restartable VACUUM design overview version 2  (Galy Lee <lee.galy@oss.ntt.co.jp>)
List 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@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: PostgreSQL - 'SKYLINE OF' clause added!
Next
From: Jim Nasby
Date:
Subject: Re: Bug: Buffer cache is not scan resistant