X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2A3D5D1ECEC for ; Wed, 24 Mar 2004 18:23:03 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 41033-06 for ; Wed, 24 Mar 2004 14:23:01 -0400 (AST) Received: from mail.unisoftbg.com (mail.unisoftbg.com [194.12.229.207]) by svr1.postgresql.org (Postfix) with ESMTP id DE428D1ED00 for ; Wed, 24 Mar 2004 14:22:57 -0400 (AST) Received: (qmail 5059 invoked by uid 507); 24 Mar 2004 19:27:43 -0000 Received: from unknown (HELO t1.unisoftbg.com) (pginfo%t1.unisoftbg.com@194.12.229.193) by 0 with SMTP; 24 Mar 2004 19:27:43 -0000 Message-ID: <4061C0A3.6C0E1C10@t1.unisoftbg.com> Date: Wed, 24 Mar 2004 18:08:51 +0100 From: pginfo X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: "scott.marlowe" Cc: "pgsql-performance@postgresql.org" Subject: Re: slow vacuum performance References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/356 X-Sequence-Number: 6212 scott.marlowe wrote: > On Wed, 24 Mar 2004, pginfo wrote: > > > Hi, > > > > scott.marlowe wrote: > > > > > On Wed, 24 Mar 2004, pginfo wrote: > > > > > > > Hi, > > > > > > > > I am running pg 7.4.1 on linux box. > > > > I have a midle size DB with many updates and after it I try to run > > > > vacuum full analyze. > > > > > > Is there a reason to not use just regular vacuum / analyze (i.e. NOT > > > full)? > > > > > > > Yes, in case I make massive updates (only in my case of cource) for example > > 2 M rows, I do not expect to have 2M new rows in next 180 days.That is the > > reaso for running vacuum full. > > My idea was to free unneedet space and so to have faster system. > > It is possible that I am wrong. > > It's all about percentages. If you've got an average of 5% dead tuples > with regular vacuuming, then full vacuums won't gain you much, if > anything. If you've got 20 dead tuples for each live one, then a full > vacuum is pretty much a necessity. The generally accepted best > performance comes with 5 to 50% or so dead tuples. Keep in mind, having a > few dead tuples is actually a good thing, as your database won't grow then > srhink the file all the time, but keep it in a steady state size wise. thanks for the good analyze,ivan.