Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C84A364FC27 for ; Tue, 30 Dec 2008 05:06:39 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 59799-01 for ; Tue, 30 Dec 2008 05:06:34 -0400 (AST) Received: from mx3.hub.org (mx3.hub.org [206.223.169.73]) by mail.postgresql.org (Postfix) with ESMTP id EFBF964FC2D for ; Tue, 30 Dec 2008 05:06:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from viefep18-int.chello.at (viefep16-int.chello.at [62.179.121.36]) by mx3.hub.org (Postfix) with ESMTP id 37E4037B7F1 for ; Tue, 30 Dec 2008 05:06:33 -0400 (AST) Received: from edge01.upc.biz ([192.168.13.236]) by viefep16-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20081230090600.CLFY1339.viefep16-int.chello.at@edge01.upc.biz> for ; Tue, 30 Dec 2008 10:06:00 +0100 Received: from [192.168.1.104] ([89.134.230.11]) by edge01.upc.biz with edge id xM5z1a03b0FQLHV01M60YD; Tue, 30 Dec 2008 10:06:00 +0100 X-SourceIP: 89.134.230.11 Message-ID: <4959E477.9050700@shopzeus.com> Date: Tue, 30 Dec 2008 10:05:59 +0100 From: Laszlo Nagy User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Subject: Big index sizes Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.125 tagged_above=0 required=5 tests=DNS_FROM_RFC_BOGUSMX=2.125 X-Spam-Level: ** X-Archive-Number: 200812/224 X-Sequence-Number: 32260 We have serveral table where the index size is much bigger than the table size. Example: select count(*) from product_price -- 2234244 Table size: 400 MB Index size: 600 MB After executing "reindex table product_price", index size reduced to 269MB. I believe this affects performance. Vacuuming a table does not rebuild the indexes, am I right? I'm not sure if I need to do this manually, or is this the result of another problem? (For example, too many open transactions, frequent updates?) Thanks