Re: postgresql meltdown on PlanetMath.org
Aaron Krowne <akrowne@vt.edu>
From: Aaron Krowne <akrowne@vt.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sean Chittenden <sean@chittenden.org>, pgsql-performance@postgresql.org
Date: 2003-03-18T02:31:22Z
Lists: pgsql-performance
I should have paid more attention to the disk space before... but it looks like somewhere between half a gig and a gig was freed! The disk footprint is about a gig now. Aaron Krowne On Sun, Mar 16, 2003 at 03:37:32AM -0500, Tom Lane wrote: > 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? > > regards, tom lane