On Sun, Feb 9, 2014 at 7:32 PM, Sergey Konoplev <gray...@gmail.com> wrote: > On Fri, Feb 7, 2014 at 10:47 AM, Claudio Freire <klaussfre...@gmail.com> > wrote: >> What I'm seeing, though, is not that, but bloat proportional to table >> size (always stuck at about 65% bloat). What's weird, is that vacuum >> full does the trick of reducing table size and bloat back to 0%. I >> haven't had time yet to verify whether it goes back to 65% after >> vacuum full (that will take time, maybe a month). > > Try pgcompact, it was designed particularily for such cases like yours > https://github.com/grayhemp/pgtoolkit.
It's a pity that that requires several sequential scans of the tables. For my case, that's probably as intrusive as the exclusive locks. I noticed I didn't mention, but the tables involved are around 20-50GB in size. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
