Re: Unbalanced Btree Indices ... - Mailing list pgsql-hackers

From Arthur Ward
Subject Re: Unbalanced Btree Indices ...
Date
Msg-id 47982.68.62.129.152.1079891306.squirrel@award.gotdns.org
Whole thread Raw
In response to Re: Unbalanced Btree Indices ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> "Marc G. Fournier" <scrappy@postgresql.org> writes:
>> Pointers to docs that I'm not finding most acceptable ...
>
> There aren't any, because at the time the 7.4 docs were being prepared,
> we didn't have enough field experience to know whether its version of
> index compaction would eliminate the practical need for REINDEX or not.
> So the docs are intentionally vague.
>
> We still haven't gotten a lot of feedback about the point from 7.4
> users.  Maybe no news is good news, or maybe it isn't ...

While upgrading from 7.4.1 to 7.4.2 last week, our production system
dropped at least 2GB during a vacuum full, and a reindex following that
also dropped about 2GB. Does that count as index bloat? It "feels" like
it's much better than 7.3.x, but it could also be my imagination. I wasn't
watching the details of the vacuum since I was mostly interested in
whether pg_autovacuum was keeping up and/or whether our FSM settings
needed an increase.

If there's some particular metric for index bloat that you can rattle off
the top of your head, I'll be glad to report back on it in another weekend
or two, when we've had some time to build up some bloat again.



pgsql-hackers by date:

Previous
From: Kris Jurka
Date:
Subject: execute command tag including affected rows count
Next
From: Tom Lane
Date:
Subject: Reporting errors inside plpgsql/SPI queries