X-Original-To: pgsql-performance@postgresql.org Received: from cat (adsl-66-123-169-52.dsl.sntc01.pacbell.net [66.123.169.52]) by postgresql.org (Postfix) with ESMTP id 5EB2F475FD9 for ; Mon, 17 Mar 2003 13:33:29 -0500 (EST) Received: by cat (Postfix, from userid 501) id 95758B6D69; Mon, 17 Mar 2003 10:33:27 -0800 (PST) Date: Mon, 17 Mar 2003 10:33:27 -0800 From: Max Baker To: Tom Lane Cc: Aaron Krowne , Sean Chittenden , pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org Message-ID: <20030317183327.GC25487@warped.org> References: <20030316060125.GD19570@vt.edu> <20030316061208.GA62529@perrin.int.nxad.com> <20030316080601.GF19570@vt.edu> <20030316082024.GA66903@perrin.int.nxad.com> <20030316083011.GG19570@vt.edu> <19394.1047803852@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19394.1047803852@sss.pgh.pa.us> User-Agent: Mutt/1.5.3i X-Archive-Number: 200303/120 X-Sequence-Number: 1418 On Sun, Mar 16, 2003 at 03:37:32AM -0500, Tom Lane wrote: > Aaron Krowne writes: > > So, either it is broken, or doing a VACUUM FULL ANALYZE rather than just > > VACUUM ANALYZE made all the difference. Is this possible (the latter, > > we know the former is possible...)? > > If your FSM parameters in postgresql.conf are too small, then plain > vacuums might have failed to keep up with the available free space, > leading to a situation where vacuum full is essential. Did you happen > to notice whether the vacuum full shrunk the database's disk footprint > noticeably? I was having a similar problem a couple threads ago, and a VACUUM FULL reduced my database from 3.9 gigs to 2.1 gigs ! So my question is how to (smartly) choose an FSM size? thanks, max`