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 8C0C8D1B509 for ; Wed, 17 Sep 2003 20:24:49 +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 95966-02 for ; Wed, 17 Sep 2003 17:24:39 -0300 (ADT) Received: from wight.ymogen.net (unknown [217.27.240.153]) by svr1.postgresql.org (Postfix) with SMTP id 8F7CED1B4FE for ; Wed, 17 Sep 2003 17:24:36 -0300 (ADT) Received: (qmail 11363 invoked from network); 17 Sep 2003 20:24:38 -0000 Received: from dsl-217-155-239-51.zen.co.uk (HELO finisterre) (217.155.239.51) by wight.ymogen.net with SMTP; 17 Sep 2003 20:24:38 -0000 From: "Matt Clark" To: , Subject: Re: Is there a reason _not_ to vacuum continuously? Date: Wed, 17 Sep 2003 21:24:37 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-reply-to: <200309171313.31078.josh@agliodbs.com> Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/251 X-Sequence-Number: 3617 > 2) Are you sure that ANALYZE is needed? Vacuum is required > whenever lots of > rows are updated, but analyze is needed only when the *distribution* of > values changes significantly. You are right. I have a related qn in this thread about random vs. monotonic values in indexed fields. > 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. I understand this needs an exclusive lock on the whole table, which is simply not possible more than once a month, if that... Workarounds/hack suggestions are more than welcome :-) Ta M