From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postmaster processes taking all the CPU |
Date: | 2007-06-08 21:57:50 |
Message-ID: | 20070608215750.GB19130@phlogiston.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jun 08, 2007 at 05:11:44PM -0400, Ericson Smith wrote:
>
> Also, if you're updating that table frequently, lots of dead tuples
> will remain in there if you don't do a VACUUM FULL regularly.
No, they won't. No well-tuned postgres installation has needed
VACUUM FULL in a long time. VACUUM FULL is there to save you if
you've overshot the regular VACUUM capabilities. This is all
explained in the manual.
> You might also want to do a dump and restore as well to prevent
> transaction wraparound.
You better not need this any more, either, if you're doing regular
VACUUM. That hasn't been a problem since 7.2.
A
--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
When my information changes, I alter my conclusions. What do you do sir?
--attr. John Maynard Keynes
From | Date | Subject | |
---|---|---|---|
Next Message | MC Moisei | 2007-06-08 22:08:26 | Re: Postmaster processes taking all the CPU |
Previous Message | Marc Mamin | 2007-06-08 21:56:54 | Re: Postmaster processes taking all the CPU |