Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 56C8B633109 for ; Thu, 1 Apr 2010 10:47:28 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 20122-05 for ; Thu, 1 Apr 2010 13:47:17 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pz0-f172.google.com (mail-pz0-f172.google.com [209.85.222.172]) by mail.postgresql.org (Postfix) with ESMTP id 970E4632CA9 for ; Thu, 1 Apr 2010 10:47:17 -0300 (ADT) Received: by pzk2 with SMTP id 2so1017276pzk.19 for ; Thu, 01 Apr 2010 06:47:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=GKCg+u9htrZMl3LiGbsRnl5OCseWBOcJxRm+XSIhNGE=; b=kNuJZmi0P4Qj5eEb5WTUUtdwFLG1jGHji9MibtSrhD9E43xlfKPgFDk9mAEbdXRAEb O+a+XHguZ9uoqA8pDNxT8QoxuYpjUlPzc+NB7kQxdkPJPUIwa08Oun8RegGWkRMYPVdg qZnqtHS26xSlv4VwZCMgpZ612CJuZn8Wjl+Ak= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wx5YGhhPJk+9/qpe+4cpngAIqh4ILd1VSpfSLShfRC5pEKEOd4weFCtGoDQAStQVe+ 2sTThjOYw2T6mUlwdrXcbRkxJJMOH6eWyxyH/LSNihgY6Vk0vjHnwh6z0+HqOxVsSlYK NfEnkHgQrfy0hKpeAEemWuaUckKGTNkNr9LwQ= MIME-Version: 1.0 Received: by 10.140.178.4 with HTTP; Thu, 1 Apr 2010 06:47:15 -0700 (PDT) In-Reply-To: References: <4BB3722F02000025000302BF@gw.wicourts.gov> <4BB40EE8.2080005@postnewspapers.com.au> <4BB47F15.4000307@netwolves.com> Date: Thu, 1 Apr 2010 19:17:15 +0530 Received: by 10.141.15.5 with SMTP id s5mr387511rvi.177.1270129635319; Thu, 01 Apr 2010 06:47:15 -0700 (PDT) Message-ID: Subject: Re: How to fast the REINDEX From: raghavendra t To: Pierre C , Kevin Grittner , greg@2ndquadrant.com, hannu@2ndquadrant.com, sclark@netwolves.com, craig@postnewspapers.com.au, jorge_montero@homedecorators.com Cc: pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=000e0cd106c0bb62d904832d19f8 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.002 tagged_above=-10 required=5 tests=BAYES_50=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201004/6 X-Sequence-Number: 38256 --000e0cd106c0bb62d904832d19f8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi All, System Config --------------------- CPU - Intel=AE Xenon=AE CPU CPU Speed - 3.16 GHz Server Model - Sun Fire X4150 RAM-Size - 16GB > Steve: So am I to understand I don't need to do daily reindexing as a maintenance > measure with 8.3.7 on FreeBSD. My question is something like Steve's, why we should not do reindexing as our maintenance task. I was doing reindex only to get a best fit and not fall short of 90% hole, bcoz my table has lot of updates and deletes. We also has the weekly maintance of VACUUM, but still reindex takes lot of time. Present Paramters settings ---------------------------------------- maintainence_work_mem - 1GB Checkpoint_segment and Wal_buffers are default values. Kevin, Pierre, Greg, Steve, Hannu, Jorge ----- Thank you for your wonderfull support and giving me the correct picture on REINDEX on this thread. I appoligies if i couldnt have shared the proper information in resolving my issue. Is the above information provided by me will help out i= n tuning better. Regards Raghavendra On Thu, Apr 1, 2010 at 5:55 PM, Pierre C wrote: > > So am I to understand I don't need to do daily reindexing as a maintenanc= e >> measure with 8.3.7 on FreeBSD. >> > > Sometimes it's better to have indexes with some space in them so every > insert doesn't hit a full index page and triggers a page split to make so= me > space. > Of course if the index is 90% holes you got a problem ;) > > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org= ) > > > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > --000e0cd106c0bb62d904832d19f8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hi All,
=A0
System Config
---------------------
CPU - Intel=AE Xenon=AE CPU
CPU Speed - 3.= 16 GHz
Server Model - Sun Fire X4150
RAM-Size - 16GB
Steve:
So am I to understand I don'= t need to do daily reindexing as a maintenance measure with 8.3.7 on FreeBS= D.
=A0
My question is=A0something like Steve's, why we should not do rein= dexing as our maintenance task. I was doing reindex only to get
a best fit and not fall short of 90% hole, bcoz my table has lot of up= dates and deletes. We also has the weekly maintance of VACUUM, but still re= index takes lot of time.
=A0
Present Paramters settings
----------------------------------------
maintainence_work_mem - 1GB
Checkpoint_segment and Wal_buffers are default values.
=A0
=A0
Kevin, Pierre, Greg, Steve, Hannu, Jorge=A0-----=A0=A0 Thank=A0you for= your wonderfull support and=A0giving me the correct picture on REINDEX on = this thread. I appoligies if i couldnt have shared the proper information i= n resolving my issue. Is the above information provided by me will help out= in tuning better.
=A0
Regards
Raghavendra
=A0
=A0
=A0
=A0
On Thu, Apr 1, 2010 at 5:55 PM, Pierre C <lists@peufeu.com>= wrote:

So am I to understand I don'= t need to do daily reindexing as a maintenance measure with 8.3.7 on FreeBS= D.

Sometimes it's better to have indexes with some = space in them so every insert doesn't hit a full index page and trigger= s a page split to make some space.
Of course if the index is 90% holes y= ou got a problem ;)



--
Sent via pgsql-performance mailing list (pgsql-performance@po= stgresql.org)=20

To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
=

--000e0cd106c0bb62d904832d19f8--