X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id C4012D1B4F0 for ; Thu, 18 Sep 2003 08:25:14 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 11037-04 for ; Thu, 18 Sep 2003 05:24:43 -0300 (ADT) Received: from houston.familyhealth.com.au (fhnet.arach.net.au [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id 0CB4AD1B4EE for ; Thu, 18 Sep 2003 05:24:40 -0300 (ADT) Received: from mars (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (8.12.9/8.12.9) with SMTP id h8I8ONa3031285; Thu, 18 Sep 2003 16:24:25 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Message-ID: <003f01c37dbe$4b6f9d10$2800a8c0@mars> From: "Christopher Kings-Lynne" To: "Oliver Scheit" , References: Subject: Re: Is there a reason _not_ to vacuum continuously? Date: Thu, 18 Sep 2003 16:24:32 +0800 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 postgresql.org X-Archive-Number: 200309/260 X-Sequence-Number: 3626 > 3) using PG 7.3 or less, you will also need to REINDEX these > tables+indexes often (daily?). This issue will go away > in 7.4, which should make you an early adopter of 7.4. Try monthly maybe. > Is this true? Haven't heard of this before. > If so, how can this be managed in a cronjob? > For the hourly VACUUM there's vacuumdb, but is > there somehting similar like reindexdb ? Yes, there is reindexdb :) Chris