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 1A850D1B561 for ; Thu, 14 Aug 2003 19:30:30 +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 48213-06 for ; Thu, 14 Aug 2003 16:29:59 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 65BE8D1C984 for ; Thu, 14 Aug 2003 16:29:57 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h7EJS45H006955; Thu, 14 Aug 2003 15:28:04 -0400 (EDT) To: jeremy.guthrie@berbee.com Cc: pgsql-performance@postgresql.org Subject: Re: Vacuum performance question In-reply-to: <200308141255.36225.jeremy.guthrie@berbee.com> References: <200308141255.36225.jeremy.guthrie@berbee.com> Comments: In-reply-to "Jeremy M. Guthrie" message dated "Thu, 14 Aug 2003 12:55:32 -0500" Date: Thu, 14 Aug 2003 15:28:04 -0400 Message-ID: <6954.1060889284@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/268 X-Sequence-Number: 3084 "Jeremy M. Guthrie" writes: > In some cases the operation of my software goes from 1-3 second runtime to > 300+ seconds during a vacuum. That seems like a lot. I concur with the nearby recommendation to reduce vacuum_mem, but I think there may be another problem. You should watch top, iostat, vmstat during a vacuum to try to see what resource is getting saturated. > I'm runing 7.3.2 and I am upgrading to 7.3.3 next week. 7.3.4, please. 7.3.3 has at least one nasty bug. regards, tom lane