pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: mikeo <mikeo@spectrumtelecorp.com>
To: pgsql-sql@postgresql.org
Subject: short query becomes long
Date: Thu, 01 Jun 2000 14:24:39 -0400
Message-ID: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com> (raw)
In-Reply-To: <6979.959788405@sss.pgh.pa.us>
References: <Pine.LNX.4.10.10005311006160.15209-100000@ns.rl.cesnet.cz>
	<Pine.LNX.4.10.10005311006160.15209-100000@ns.rl.cesnet.cz>

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 




view thread (2+ messages)  latest in thread

Message-ID: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com>
Permalink:  ../3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com/
Also on:    postgresql.org/message-id/3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: mikeo@spectrumtelecorp.com
  Subject: Re: short query becomes long
  In-Reply-To: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com>
  References: <Pine.LNX.4.10.10005311006160.15209-100000@ns.rl.cesnet.cz> <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox