X-Original-To: pgsql-performance@postgresql.org Received: from perrin.int.nxad.com (unknown [69.1.70.251]) by postgresql.org (Postfix) with ESMTP id 580F0475AD4 for ; Sun, 16 Mar 2003 03:36:17 -0500 (EST) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id E1E702107E; Sun, 16 Mar 2003 00:35:37 -0800 (PST) Date: Sun, 16 Mar 2003 00:35:37 -0800 From: Sean Chittenden To: Aaron Krowne Cc: pgsql-performance@postgresql.org Subject: Re: postgresql meltdown on PlanetMath.org Message-ID: <20030316083537.GB66903@perrin.int.nxad.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030316083011.GG19570@vt.edu> User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ X-Archive-Number: 200303/107 X-Sequence-Number: 1405 > > 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 =) Cool, glad to hear other installations are picking up doing this. > 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...)? You shouldn't have to do a VACUUM FULL. Upgrade your PostgreSQL installation if you can (most recent if possible), there have been many performance updates and VACUUM fixes worth noting. Check the release notes starting with your version and read through them up to the current release... you'll be amazed at all the work that's been done, some of which it looks like may affect your installation. http://developer.postgresql.org/docs/postgres/release.html -sc -- Sean Chittenden