Will this help with performance ?
Depends if the bloat is in part of your working set. If debloating can
make the working set fit in RAM, or lower your IOs, you'll get a boost.
Now, is the bloat in the tables (which tables ?) or in the indexes
(which indexes ?), or in the toast tables perhaps, or in the system
catalogs or all of the above ? Or perhaps there is a long-forgotten
process that got zombified while holding a huge temp table ? (not very
likely, but who knows).
Use pg_relation_size() and its friends to get an idea of the size
of stuff.
I'll look into that, thanks
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
