From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Aaron Krowne <akrowne@vt.edu>
Cc: Sean Chittenden <sean@chittenden.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgresql meltdown on PlanetMath.org
Date: 17 Mar 2003 10:58:39 -0500
Message-ID: <87hea2assw.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <19394.1047803852@sss.pgh.pa.us>
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>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Aaron Krowne <akrowne@vt.edu> 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?
This seems to be a frequent problem.
Is there any easy way to check an existing table for lost free space?
Is there any way vauum could do this check and print a warning suggesting
using vaccuum full and/or increasing fsm parameters if it finds such?
--
greg
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: gsstark@mit.edu, tgl@sss.pgh.pa.us, akrowne@vt.edu, sean@chittenden.org
Subject: Re: postgresql meltdown on PlanetMath.org
In-Reply-To: <87hea2assw.fsf@stark.dyndns.tv>
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> <87hea2assw.fsf@stark.dyndns.tv>
* 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