X-Original-To: pgsql-performance@postgresql.org Received: from citidel1 (elaine.dlib.vt.edu [128.173.49.40]) by postgresql.org (Postfix) with ESMTP id 98B334762E0 for ; Mon, 17 Mar 2003 21:31:40 -0500 (EST) Received: from akrowne by citidel1 with local (Exim 3.34 #1 (Debian)) id 18v6ss-0001ef-00; Mon, 17 Mar 2003 21:31:22 -0500 Date: Mon, 17 Mar 2003 21:31:22 -0500 From: Aaron Krowne To: Tom Lane Cc: Sean Chittenden , pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org Message-ID: <20030318023122.GN3703@vt.edu> Reply-To: Aaron Krowne 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.3.27i X-Archive-Number: 200303/129 X-Sequence-Number: 1427 I should have paid more attention to the disk space before... but it looks like somewhere between half a gig and a gig was freed! The disk footprint is about a gig now. Aaron Krowne 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? > > regards, tom lane