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 1C509D1B7C6 for ; Wed, 16 Jun 2004 01:56:22 -0300 (ADT) 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 20285-01 for ; Wed, 16 Jun 2004 04:56:21 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 230F9D1B7C1 for ; Wed, 16 Jun 2004 01:56:19 -0300 (ADT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id i5G4u9t04728; Wed, 16 Jun 2004 13:56:09 +0900 Message-ID: <009601c4535e$3e8d10c0$7201a8c0@mst1x5r347kymb> From: "Iain" To: "C. Bensend" , References: <51429.63.227.74.41.1087347504.squirrel@webmail.stinkweasel.net> <15549.1087351669@sss.pgh.pa.us> <50124.63.227.74.41.1087351971.squirrel@webmail.stinkweasel.net> <15996.1087354312@sss.pgh.pa.us> <58063.63.227.74.41.1087355391.squirrel@webmail.stinkweasel.net> Subject: Re: VARCHAR -vs- CHAR: huge performance difference? Date: Wed, 16 Jun 2004 13:56:11 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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: 200406/196 X-Sequence-Number: 13856 > Or do I just need to vacuum more often? I _did_ try a vacuum before > asking the list for help, but it didn't give any improvement (just a > vacuum analyze). "vacuum analyse" allows dead space to be re-used, but doesn't compact the table, you need "vacuum analyse full" for that. I'm not sure how the free space map relates to this, maybe someone can shed some light, but if it is too small, not all dead rows can be re-used (as I understand it). If your table (or even the DB in general) is updated alot, the default FSM size that comes with 7.3 may not be enough to ensure the most efficient space reclamation. Last time I looked the docs were a little hazy on that.