From: Tom Lane <tgl@sss.pgh.pa.us>
To: mikeo <mikeo@spectrumtelecorp.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: short query becomes long
Date: Thu, 01 Jun 2000 22:31:59 -0400
Message-ID: <9845.959913119@sss.pgh.pa.us> (raw)
In-Reply-To: <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com>
References: <Pine.LNX.4.10.10005311006160.15209-100000@ns.rl.cesnet.cz>
<Pine.LNX.4.10.10005311006160.15209-100000@ns.rl.cesnet.cz>
<3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com>
mikeo <mikeo@spectrumtelecorp.com> 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
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: tgl@sss.pgh.pa.us, mikeo@spectrumtelecorp.com
Subject: Re: short query becomes long
In-Reply-To: <9845.959913119@sss.pgh.pa.us>
References: <Pine.LNX.4.10.10005311006160.15209-100000@ns.rl.cesnet.cz> <3.0.1.32.20000601142439.0094b320@pop.spectrumtelecorp.com> <9845.959913119@sss.pgh.pa.us>
* 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