Re: Preventing duplicate vacuums?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Rod Taylor <pg(at)rbt(dot)ca>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Preventing duplicate vacuums?
Date: 2004-02-05 21:41:25
Message-ID: 200402051341.25089.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Berkus
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-02-05 21:44:37 Re: [PATCHES] log session end - again
Previous Message Alvaro Herrera 2004-02-05 21:36:19 Re: It's past time to redo the smgr API