| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Hartman, Matthew" <Matthew(dot)Hartman(at)krcc(dot)on(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Vacuum on the database versus individual tables. |
| Date: | 2009-06-25 17:31:49 |
| Message-ID: | dcc563d10906251031w549e1e78vf35472d79287f6eb@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jun 25, 2009 at 8:40 AM, Hartman,
Matthew<Matthew(dot)Hartman(at)krcc(dot)on(dot)ca> wrote:
> Good morning.
>
> On occasion I’ll perform a full vacuum on a database but will still receive
> a suggestion to vacuum an individual table immediately after. Does the full
> database vacuum not handle each individual table?
Wait, is this a regular vacuum against the whole database, or a vacuum
FULL against the whole database? Or a vacuum full on an individual
table. Vacuum full is generally not recommended for regular
maintenance, but only for getting out of bloat problems that regular
vacuum can no longer handle. It is generally best followed by a
reindex to clean up the indexes.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jack W | 2009-06-25 18:30:50 | Need suggestions |
| Previous Message | Scott Marlowe | 2009-06-25 17:28:55 | Re: horizontal sharding |