X-Original-To: pgsql-performance@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 79DC1475AE5 for ; Sun, 16 Mar 2003 03:37:32 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2G8bWub019395; Sun, 16 Mar 2003 03:37:32 -0500 (EST) To: Aaron Krowne Cc: Sean Chittenden , pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org In-reply-to: <20030316083011.GG19570@vt.edu> 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> Comments: In-reply-to Aaron Krowne message dated "Sun, 16 Mar 2003 03:30:11 -0500" Date: Sun, 16 Mar 2003 03:37:32 -0500 Message-ID: <19394.1047803852@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/108 X-Sequence-Number: 1406 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