Shaun Thomas <[EMAIL PROTECTED]> writes:
> Actually, on a whim, I dumped that 520MB database to it's 5MB file, and
> reimported it into an entirely new DB. It was 14MB. We vacuum at least
> once an hour (we have a loader that runs every hour, it may run multiple
> concurrent insert scripts). We also use vacuum analyze. So, I really
> can't see a reason for it to balloon to that horridly expanded size.
>
> Maybe stale indexes? Aborted vacuums? What on earth would cause that?
VACUUM doesn't currently vacuum indexes. Yes, it's a serious wart. :(
That's why the data file size declined so much (modulo WAL stuff).
I suggest drop/recreate the indexes at intervals. Or try REINDEX,
which may work better.
-Doug
--
Free Dmitry Sklyarov!
http://www.freesklyarov.org/
We will return to our regularly scheduled signature shortly.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
