Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA54507 for ; Thu, 1 Jun 2000 22:32:17 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id WAA09848; Thu, 1 Jun 2000 22:31:59 -0400 (EDT) To: mikeo cc: pgsql-sql@postgresql.org Subject: Re: short query becomes long In-reply-to: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com> References: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com> Comments: In-reply-to mikeo message dated "Thu, 01 Jun 2000 14:24:39 -0400" Date: Thu, 01 Jun 2000 22:31:59 -0400 Message-ID: <9845.959913119@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/12 mikeo writes: > after about 50,000 updates, which fly right along, the process begins > to really bog down. we perform a vacuum analzye and it speeds right > up again. A plain "vacuum" should do the job in a bit less time. The problem is you need to reclaim the space occupied by deleted versions of rows. No way around that with the current storage manager: vacuum is the only way to get rid of the wasted space. regards, tom lane