decibel <deci...@decibel.org> wrote: > *any* step that improves dealing with table bloat is extremely > welcome, as right now you're basically stuck rebuilding the table. +1 Although, possibly more irritating than actually rebuilding it is evaluating borderline bloat situations to determine if they will "work themselves out" over time or whether you need to bite the bullet to do aggressive maintenance. Having some way for routine vacuums (or any other routine process, currently available or that could be scheduled) to "nibble away" at moderate bloat without significant performance or usability impact would make life easier for at least *some* DBAs. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
