Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 6B9B065014A for ; Fri, 17 Oct 2008 13:05:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 07842-06 for ; Fri, 17 Oct 2008 13:05:27 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by postgresql.org (Postfix) with ESMTP id 9C71365013E for ; Fri, 17 Oct 2008 13:05:27 -0300 (ADT) Received: by wf-out-1314.google.com with SMTP id 25so668181wfc.28 for ; Fri, 17 Oct 2008 09:05:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=sfFcvWv8ZafEW2Uw3A1HjOSiBQuxfxrBBAPuP6dhf+Q=; b=JtgEr+BAWLpmBrhllgzbCAIyY/jHdy6dMv5Zoh8NYJtci01rxls9oy3Z67qpeYsaeP ScGAVyEQ/r2fZyBrtm15k88sYrug8F5gehWwpw4DFDGjNMipMfi5IxvimTo5HUlDl6Se ezhZ37LjwbqF15CUBdVVzv0HiljrVUAWiwEb0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=k5HcGtY5kToJIsPtrbpFTedyucBA4CYjIAm/fCp0J7LP+2tQCPIX58fU6k2tZnpWY8 kdP6ErD59ofMXyxJyolhkKIr0mSf3eRHSzQ1mBpV/HaPqA5eq/HHfh1kehWFiUCiFZuJ I02LMnDSGgW5Xx4Uu1ZTGUztffBtbNBttnsz8= Received: by 10.115.58.18 with SMTP id l18mr3486949wak.177.1224259526599; Fri, 17 Oct 2008 09:05:26 -0700 (PDT) Received: by 10.114.127.18 with HTTP; Fri, 17 Oct 2008 09:05:26 -0700 (PDT) Message-ID: <8a547c840810170905m7323dbd8x90de7dd004abc7d4@mail.gmail.com> Date: Fri, 17 Oct 2008 09:05:26 -0700 From: "Tory M Blue" To: pgsql-performance@postgresql.org Subject: Index bloat, reindex weekly, suggestions etc? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/90 X-Sequence-Number: 31671 Good day, So I've been running 8.3 for a few months now and things seem good. I also note there are some bug fixes and you are up to 8.3.4 now, but reading it I don't see that I'm being affected by anything, but please tell me if i should plan upgrades to 8.3.4.. The real issue is my index growth and my requirement for weekly re-indexing (which blocks and therefore is more or less a manual process in a live production environment (fail over, changing vips etc). After Reindex My data 3.1G /data/cls My Indexes 1.5G /data/clsindex After 2 weeks My data 3.4G /data/cls My indexes 6.8G /data/clsindex This is 2 weeks. and throughout those 2 weeks I can see performance degrading. In fact I just bumped the memory footprint of my server to 32gigs from 8gigs as my entire PostgreSQL DB is now 15gb, this has helped tremendously, everything ends up in memory and there is almost zero read access from the DB (that's great), however as my DB grows I can't expect to manage it by adding Terabytes of memory to the system, so something is not being done efficiently. We are testing with fill factor, but that just seems to allocate space and doesn't really decrease my index size on disk. It does however seem to help performance a bit, but not a ton. Where should I start looking, what type of information should I provide in order for me to help you, help me? This is a transactional DB with over 800K updates happening each day. tons of updates and deletes. autovac is on and I do a analyze each night after the dump Thanks Tory