Re: Frequently updated tables - Mailing list pgsql-hackers

From pgsql@mohawksoft.com
Subject Re: Frequently updated tables
Date
Msg-id 56883.64.119.142.34.1086802887.squirrel@mail.mohawksoft.com
Whole thread Raw
In response to Re: Frequently updated tables  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: Frequently updated tables
Re: Frequently updated tables
Re: Frequently updated tables
Re: Frequently updated tables
List pgsql-hackers
> On Wed, Jun 09, 2004 at 10:49:20PM +0800, Christopher Kings-Lynne wrote:
>> >I love PG, I've been using it since version 6x, and it has gotten
>> >fantastic over the years, and in many cases, I would choose it over
>> >Oracle, but for systems that need frequent updates, I have a lot of
>> >concerns.
>>
>> ...that's the price you pay for concurrency man...
>
> Also he said that the problem was solved with enough lazy VACUUM
> scheduling.  I don't understand why he doesn't want to use that
> solution.
>

Sigh, because vacuums take away from performance. Imagine a table that has
to be updated on the order of a few thousand times a minute. Think about
the drop in performance during the vacuum.

On a one row table, vacuum is not so bad, but try some benchmarks on a
table with a goodly number of rows.


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: sequences and "addval('myseq', value)"
Next
From: Jan Wieck
Date:
Subject: Re: thread safety tests