Re: Preventing duplicate vacuums? - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Preventing duplicate vacuums?
Date
Msg-id 200402051341.25089.josh@agliodbs.com
Whole thread Raw
In response to Re: Preventing duplicate vacuums?  (Rod Taylor <pg@rbt.ca>)
List pgsql-hackers
Rod,

> You have a 8 billion row table with some very high turn over tuples
> (lots of updates to a few thousand rows). A partial or targeted vacuum
> would be best, failing that you kick them off fairly frequently,
> especially if IO isn't really an issue.

Yes, but we don't have partial or targeted vacuums yet.  When tablespaces is 
finished, presumably the lock would be per tablespace.

-- 
-Josh BerkusAglio Database SolutionsSan Francisco



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: It's past time to redo the smgr API
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] log session end - again