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 D8D52475F0D for ; Sun, 16 Mar 2003 03:30:14 -0500 (EST) Received: from akrowne by citidel1 with local (Exim 3.34 #1 (Debian)) id 18uTX1-0003bB-00; Sun, 16 Mar 2003 03:30:11 -0500 Date: Sun, 16 Mar 2003 03:30:11 -0500 From: Aaron Krowne To: Sean Chittenden Cc: pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org Message-ID: <20030316083011.GG19570@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030316082024.GA66903@perrin.int.nxad.com> User-Agent: Mutt/1.3.27i X-Archive-Number: 200303/106 X-Sequence-Number: 1404 > You may want to setup a nightly vacuum/backup procedure. Palle > Girgensohn has written a really nice and simple > script that's been in use for ages on FreeBSD PostgreSQL installations > for making sure that you don't have this problem. > > Actually, it'd be really cool to lobby to get this script added to the > base PostgreSQL installation that way you wouldn't have this > problem... it'd also dramatically increase the number of nightly > backups performed for folks if a default script does this along with > vacuuming. -sc *Actually*, I just double checked, and I was not hallucinating: I *do* have a nightly vacuum script... because Debian postgres comes with it =) 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...)? apk