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                                            [EMAIL PROTECTED]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to