From: Sean Chittenden <sean@chittenden.org>
To: Aaron Krowne <akrowne@vt.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgresql meltdown on PlanetMath.org
Date: Sun, 16 Mar 2003 00:35:37 -0800
Message-ID: <20030316083537.GB66903@perrin.int.nxad.com> (raw)
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>
> > You may want to setup a nightly vacuum/backup procedure. Palle
> > Girgensohn <girgen@pingpong.net> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: sean@chittenden.org, akrowne@vt.edu
Subject: Re: postgresql meltdown on PlanetMath.org
In-Reply-To: <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> <20030316083537.GB66903@perrin.int.nxad.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox