| From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
|---|---|
| To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: partial VACUUM FULL |
| Date: | 2004-03-23 20:57:30 |
| Message-ID: | 4060A4BA.1040804@potentialtech.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joseph Shraibman wrote:
> If I cancel a VACUUM FULL, is the work that was done up until that point
> thrown away? I have a table that needs vacuuming but I can't accept the
> downtime involved in vacuuming.
Not sure about the "cancel vacuum full" question, but I had some other thoughts
for you.
Keep in mind that a plain vacuum can do a lot of good if done regularly, and
it doesn't lock tables, thus the database can be in regular use while it's
run. As a result, there is no downtime involved with regularly scheduled
vacuums.
There _can_ be a performance hit while vacuum is running, so you may need to
take that into account. But I would expect that the performance hit incurred
during running vacuum will be less than that of not running it for long
periods of time.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Thomas | 2004-03-23 21:07:32 | Re: patterns for database administration |
| Previous Message | Matthew Hixson | 2004-03-23 20:49:18 | Re: patterns for database administration |