| From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
|---|---|
| To: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
| Cc: | gsstark(at)mit(dot)edu, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: VACUUM Question |
| Date: | 2004-06-04 19:40:45 |
| Message-ID: | 20040604154045.14016347.wmoran@potentialtech.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rick Gigger <rick(at)alpinenetworking(dot)com> wrote:
> >>One more question; on one server the Vacuum Analyze before the insert takes
> >>approx. 2min after that the same command takes 15min.
> >
> >
> > You might try a VACUUM FULL sometime when you can deal with 15min of downtime
> > or so. Actually it would probably be longer. Perhaps the table that's taking
> > 15min has a ton of extra dead tuples left over from the fsm settings being too
> > low and/or vacuum being too infrequent.
>
> Does VACUUM FULL just lock entire tables and thus cause you to
> essentially have downtime on that database because it doesn't respond
> quickly or do you actually have to shut down postgres to safely do a
> vacuum full?
The former. You don't shut the database server down, but it won't be
responsive while vacuum full is running.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Penhey | 2004-06-04 19:46:12 | Backup and Restore of PostgreSQL |
| Previous Message | Rick Gigger | 2004-06-04 19:31:47 | Re: VACUUM Question |