Received: from gw.spectrumtelecorp.com (216-064-054-021.inaddr.vitts.com [216.64.54.21]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA02432 for ; Thu, 1 Jun 2000 14:16:38 -0400 (EDT) (envelope-from mikeo@spectrumtelecorp.com) Received: from spec34 (spec34.spectrumtelecorp.com [192.168.1.67]) by gw.spectrumtelecorp.com (8.9.3/8.8.7) with SMTP id OAA06801 for ; Thu, 1 Jun 2000 14:20:16 -0400 Message-Id: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com> X-Sender: mikeo@pop.spectrumtelecorp.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 01 Jun 2000 14:24:39 -0400 To: pgsql-sql@postgresql.org From: mikeo Subject: short query becomes long In-Reply-To: <6979.959788405@sss.pgh.pa.us> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200006/9 hi, we have a weird situation here. we have a table of approx. 10k rows representing accumulated activity by specific customers. as information is gathered those customers rows are updated. the number of rows does not increase unless we get a new customer so that is not a factor. the table is defined as follows: Table "account_summary_02" Attribute | Type | Modifier -------------+-------------+---------- bill_br_id | bigint | not null cust_id | varchar(15) | not null btn_id | varchar(15) | not null ln_id | varchar(15) | not null ct_key | float8 | not null as_quantity | float8 | not null as_charges | float8 | not null as_count | float8 | not null Index: account_summary_02_unq_idx the index is on the first 5 columns. here's the situation. 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. my question is, is there a way to perform these updates, potentially 500k to 1 million in a day, without having to vacuum so frequently? maybe some setting or parameter to be changed? the update query is doing an index scan. mikeo