Received: from mocha2.baileylink.net (mocha2.baileylink.net [12.152.112.28]) by postgresql.org (8.11.3/8.11.4) with SMTP id fATG5fm75333 for ; Thu, 29 Nov 2001 11:05:42 -0500 (EST) (envelope-from banghe@baileylink.net) Received: (qmail 16994 invoked from network); 29 Nov 2001 15:59:12 -0000 Received: from dhcp61.baileylink.net (HELO baileylink.net) (12.152.112.61) by mocha2.baileylink.net with SMTP; 29 Nov 2001 15:59:12 -0000 Message-ID: <3C065CEA.B23D9745@baileylink.net> Date: Thu, 29 Nov 2001 10:06:02 -0600 From: bangh X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en,zh-CN,zh,zh-TW,pdf MIME-Version: 1.0 To: "'pgsql-admin@postgresql.org'" Subject: Vacuum References: <20011127085555.A20745-100000@megazone23.bigpanda.com> <3C04A23E.BF409D74@answare.fr> <2131.1006960265@sss.pgh.pa.us> <3C0510FF.694D34EA@answare.fr> <2528.1006965329@sss.pgh.pa.us> <3C051482.908DEDFF@answare.fr> <2775.1006967609@sss.pgh.pa.us> <3C05F979.ED76D96D@answare.fr> <18157.1007043873@sss.pgh.pa.us> <18448.1007046370@sss.pgh.pa.us> Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7bit X-Archive-Number: 200111/165 X-Sequence-Number: 2690 Hello, Using vacuum a table is very usefull to compress the space of a table . However I noticed the index grows also very fast. Does anyone have a way to compress the index? I know if I dump the database, and destroy the orginal database, then create new one using the same database, and restory the dump file, that will dramatically compress the space the database has taken. This is not a good way for a live database that is driven by the web application that means I have to shut down the web application service during this clearup. Thanks, Bangh