Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 03E61632878 for ; Thu, 1 Apr 2010 08:24:56 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 88162-04 for ; Thu, 1 Apr 2010 11:24:38 +0000 (UTC) X-Greylist: delayed 00:14:27.367189 by SQLgrey-1.7.6 Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by mail.postgresql.org (Postfix) with ESMTP id 77D366323CC for ; Thu, 1 Apr 2010 08:24:45 -0300 (ADT) Received: from [173.65.53.194] (helo=sclark66.netwolves.com) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1NxIHu-0005Hj-7v; Thu, 01 Apr 2010 06:10:14 -0500 Message-ID: <4BB47F15.4000307@netwolves.com> Date: Thu, 01 Apr 2010 07:10:13 -0400 From: Steve Clark User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3 MIME-Version: 1.0 To: Craig Ringer CC: Jaime Casanova , raghavendra t , Kevin Grittner , pgsql-performance@postgresql.org Subject: Re: How to fast the REINDEX References: <4BB3722F02000025000302BF@gw.wicourts.gov> <4BB40EE8.2080005@postnewspapers.com.au> In-Reply-To: <4BB40EE8.2080005@postnewspapers.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: a437fbc6971e80f61aa676d7e74259b7b3291a7d08dfec7918d8d0ca3dc6a6c9d7ddec58026ec3aa350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 173.65.53.194 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.299 tagged_above=-10 required=5 tests=AWL=-1.300, BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201004/2 X-Sequence-Number: 38252 On 03/31/2010 11:11 PM, Craig Ringer wrote: > Jaime Casanova wrote: >> On Wed, Mar 31, 2010 at 5:33 PM, raghavendra t >> wrote: >>>>> Why are you doing that? >>> Our table face lot of updates and deletes in a day, so we prefer reindex to >>> update the indexes as well overcome with a corrupted index. >>> >> >> do you have a corrupted index? if not, there is nothing to do... >> REINDEX is not a mantenance task on postgres > > Actually, if your free_space_map (pre 8.4) isn't up to keeping track of > bloat, or autovac isn't running enough, you're likely to get bloat of > indexes as well as tables that may need VACUUM FULL + REINDEX to > properly clean up. > > It's probably better to fix your fsm/autovac settings then CLUSTER the > table so it doesn't happen again, though. > > -- > Craig Ringer > So am I to understand I don't need to do daily reindexing as a maintenance measure with 8.3.7 on FreeBSD. -- Stephen Clark NetWolves Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark@netwolves.com www.netwolves.com