| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Rod Taylor <rbt(at)rbt(dot)ca> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com>, Postgresql Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Press Release |
| Date: | 2003-10-30 00:22:53 |
| Message-ID: | 200310291622.53733.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
Josh,
> Not if it is a vacuum full and you are trying to do an insert. Which is
> exactly what
> I am talking about. Doing a vacuum full on a table that has had 5.7 million
> inserts/updates/deletes during the last 23 hours is going to cause a rather
> long vacuum full which in turn will cause a rather long period of
> unavailability
> of the database.
But if you've set it up correctly in the first place, the vacuum full won't be
necessary.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2003-10-30 00:34:28 | Re: Press Release |
| Previous Message | Joshua D. Drake | 2003-10-30 00:08:45 | Re: Press Release |