Pallav Kalva <pkalva@deg.cc> writes:
> Tom Lane wrote:
>> Another likely problem is that you
>> need to increase the FSM settings (how big is your whole database?)
>>
> Yes, you are right this table is heavily updated, the whole database
> size is of 1.5 gigs, right now i have default fsm settings how much
> should i increase max_fsm_pages and max_fsm_relations to ?
A lot --- factor of 10 at least. Try "vacuum verbose" and look at the
last couple lines of output.
>> VACUUM FULL will fix the immediate problem. You might well find CLUSTER
>> to be a faster alternative, though.
> How does CLUSTER benefit me ?
It'll probably take less time to rebuild the table. VACUUM FULL is
really optimized for the case of moving a relatively small fraction
of the table around, but it sounds like you need a complete rebuild.
regards, tom lane
