Skip site navigation (1) Skip section navigation (2)

Re: Slow updates, poor IO

From: John Huttley <John(at)mib-infotech(dot)co(dot)nz>
To: Andrew Sullivan <ajs(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow updates, poor IO
Date: 2008-09-26 23:03:38
Message-ID: 48DD6A4A.10209@mib-infotech.co.nz (view raw or flat)
Thread:
Lists: pgsql-performance
Hi Andrew,
There are two problems.
The first is the that if there is a table with a index and an update is 
performed on a non indexed field,
the index is still re indexed. this is part of the trade-offs of MVCC.
Apparently this is documented under 'MVCC' in the manual. It should be 
documented under 'performance'

We should reasonably expect that the total amount of IO will go up, over 
a non-indexed table.

The second thing is that the disk IO throughput goes way down.

This is not an issue with MVCC, as such, except that it exposes the 
effect of a write to an indexed field.
--even if you don't expect it.

--john

Andrew Sullivan wrote:
> Hi,
>
> On Fri, Sep 26, 2008 at 07:24:55AM +1200, John Huttley wrote:
>   
>> I've just had an interesting encounter with the slow full table update 
>> problem that is inherent with MVCC
>>     
>
> Quite apart from the other excellent observations in this thread, what
> makes you think this is an MVCC issue exactly?
>
> A
>
>   

In response to

Responses

pgsql-performance by date

Next:From: John HuttleyDate: 2008-09-26 23:09:31
Subject: Re: Slow updates, poor IO
Previous:From: Scott CareyDate: 2008-09-26 15:01:17
Subject: Re: CPU load

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group