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 374FFD1CCA5 for ; Sat, 13 Mar 2004 16:11:09 +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 02148-03 for ; Sat, 13 Mar 2004 12:11:07 -0400 (AST) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id 47312D1B55C for ; Sat, 13 Mar 2004 12:11:07 -0400 (AST) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 1078182; Sat, 13 Mar 2004 08:06:36 -0800 Message-ID: <405331B0.6080102@joeconway.com> Date: Sat, 13 Mar 2004 08:07:12 -0800 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marty Scholes Cc: pgsql-performance Subject: Re: rapid degradation after postmaster restart References: <4052661D.5060505@joeconway.com> <4052771A.1080506@outputservices.com> In-Reply-To: <4052771A.1080506@outputservices.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/173 X-Sequence-Number: 6029 Marty Scholes wrote: > I have seen similar results to what you are describing. > > I found that running a full vacuum: > > vacuumdb -fza > > followed by a checkpoint makes it run fast again. > > Try timing the update with and without a full vacuum. Will do. I'll let you know how it goes. Thanks for the reply. Joe