Re: 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly over time - Mailing list pgsql-general

From Bruno Wolff III
Subject Re: 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly over time
Date
Msg-id 20040421181854.GD30712@wolff.to
Whole thread Raw
In response to 7.3.4 on Linux: UPDATE .. foo=foo+1 degrades massivly over time  (Philipp Buehler <pb-pgsql-g@mlsub.buehler.net>)
List pgsql-general
On Wed, Apr 21, 2004 at 19:52:15 +0200,
  Philipp Buehler <pb-pgsql-g@mlsub.buehler.net> wrote:
>
> While running
> UPDATE banner SET counterhalf=counterhalf+1 WHERE BannerID=50
> several thousand times, the return times degrade (somewhat linear).

This is to be expected. Postgres uses MVCC and everytime you do an update
a new row is created.

> A following VACCUM brings back return times to 'start' - but I cannot
> run VACUUM any other minute (?). And it exactly vaccums as many tuples
> as I updated.. sure thing:

Why not? You only have to vacuum this one table. Vacuuming it once a minute
should be doable.

pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: Can I reset the lower bound of an array.
Next
From: Mike Nolan
Date:
Subject: Re: PL/SQL question