X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 833F93A3C07 for ; Tue, 26 Oct 2004 01:42:25 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 40726-06 for ; Tue, 26 Oct 2004 00:42:13 +0000 (GMT) Received: from mpls-qmqp-03.inet.qwest.net (mpls-qmqp-03.inet.qwest.net [63.231.195.114]) by svr1.postgresql.org (Postfix) with SMTP id 60F793A4230 for ; Tue, 26 Oct 2004 01:42:15 +0100 (BST) Received: (qmail 15369 invoked by uid 0); 26 Oct 2004 00:42:15 -0000 Received: from mpls-pop-03.inet.qwest.net (63.231.195.3) by mpls-qmqp-03.inet.qwest.net with QMQP; 26 Oct 2004 00:42:15 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-03.inet.qwest.net with SMTP; 26 Oct 2004 00:42:15 -0000 Date: Mon, 25 Oct 2004 18:44:33 -0600 Message-Id: <1098751473.31930.11.camel@localhost.localdomain> From: "Scott Marlowe" To: "Rigmor Ukuhe" Cc: pgsql-admin@postgresql.org Subject: Re: Index relation size In-Reply-To: References: Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/341 X-Sequence-Number: 15334 On Mon, 2004-10-25 at 05:02, Rigmor Ukuhe wrote: > Hi, > > I have table with size ~35 MB, it has several indexes and couple of them are > well over 500 MB in size (they are indexes with 3-4 columns involved, with > datatypes like varchar, int4 , timestamp, boolean). > Database is VACUUMed nightly, version is 7.2.4 (cant upgrade to newest > version at the moment). Are these > index sizes indicating some problems with our Postgres server? Assuming you aren't suffering from index bloat, which was a problem in 7.2, this may be normal. To see if you are, try "reindex indexname" and see if the index shrinks. Multicolumn indexes being bigger than their table because of the way they're put together, so it's likely that when you get done reindexing the index will still be bigger than the table.