| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Preventing duplicate vacuums? |
| Date: | 2004-02-05 21:26:33 |
| Message-ID: | 1076016392.308.539.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2004-02-05 at 15:37, Josh Berkus wrote:
> Folks,
>
> Just occurred to me that we have no code to prevent a user from running two
> simultaneos lazy vacuums on the same table. I can't think of any
> circumstance why running two vacuums would be desirable behavior; how
> difficult would it be to make this an exception?
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-02-05 21:36:19 | Re: It's past time to redo the smgr API |
| Previous Message | Tom Lane | 2004-02-05 21:22:41 | Re: It's past time to redo the smgr API |