Index bloat and the need to REINDEX

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Index bloat and the need to REINDEX
Date: 2006-08-15 22:44:51
Message-ID: c2a37a715194bccec637104fc8d8da9e@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is there a better solution to the "index bloat" problem with regards
to minimizing locking while reducing an ever-growing use of disk
space? In particular, it would be nice if there was a way to force
VACUUM [FULL] to do some of the compression that REINDEX now does.

Right now, we have tables that are updated very frequently, and a
vacuum full just doesn't do much to reduce the disk space, as
the indexes keep growing until a REINDEX is done. Tried on HEAD
as well.

Thanks,
- --
Greg Sabino Mullane greg(at)endpoint(dot)com greg(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200608151719
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFE4k3PvJuQZxSWSsgRAjmHAKCDvKmDe3P7HfCmSwOTtnxpimn2EgCghhSF
bSllNWoYjSU+g3yz23N8jXI=
=0Uxr
-----END PGP SIGNATURE-----

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2006-08-15 23:15:26 Re: BugTracker (Was: Re: 8.2 features status)
Previous Message Tom Lane 2006-08-15 22:42:17 Re: [HACKERS] Forcing current WAL file to be archived