From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: More Praise for 7.4RC2 |
Date: | 2003-11-14 03:37:29 |
Message-ID: | 87wua3oc1y.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Reece Hart <reece(at)in-machina(dot)com> writes:
> On Thu, 2003-11-13 at 10:09, scott.marlowe wrote:
>
> > Do you vacuum full every so often? If not, and if you've been overflowing
> > your fsm, then your tables will just grow without shrinking.
> > Also, index growth could be a problem.
>
>
> Hmm. I didn't realize that I needed to vacuum full as well -- I thought
> vacuum was sufficient for performance gains, and that full reclaimed
> space but didn't result in significant performance gains.
plain Vacuum is sufficient if the amount of free space it finds fits within
the free space map. During normal use with frequent vacuums on a system with
well-tuned fsm parameters that should be true.
However on a big heavily used database where the fsm parameters haven't been
raised from the defaults it's possible that it isn't. And on a table where
large batch updates or deletes have been run it's possible to require a vacuum
full after the batch job creates lots of dead tuples.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Ma Siva Kumar | 2003-11-14 03:43:05 | Re: multibyte support [Resolved] |
Previous Message | jini us | 2003-11-14 03:28:00 | Re: embedded postgresql + C++ IDE |