From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pallav Kalva <pkalva@deg.cc>
Cc: pgsql-performance@postgresql.org
Subject: Re: Poor Performance on a table
Date: Thu, 02 Dec 2004 15:10:49 -0500
Message-ID: <702.1102018249@sss.pgh.pa.us> (raw)
In-Reply-To: <41AF72EB.1070900@deg.cc>
References: <41AF68F2.1050206@deg.cc>
<29227.1102016219@sss.pgh.pa.us>
<41AF72EB.1070900@deg.cc>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, pkalva@deg.cc
Subject: Re: Poor Performance on a table
In-Reply-To: <702.1102018249@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox