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

Re: Slow updates, poor IO

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Huttley <John(at)mib-infotech(dot)co(dot)nz>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow updates, poor IO
Date: 2008-09-28 14:33:08
Message-ID: 6110.1222612388@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
John Huttley <John(at)mib-infotech(dot)co(dot)nz> writes:
> Scott Marlowe wrote:
>> was...  was a part of the trade-offs.

> You are thinking of HOT?
> I don't think it applies in the case of full table updates??

Sure, as long as there's enough free space on each page.

If you wanted to make a table that was optimized for this kind of thing,
you could try creating it with fillfactor 50.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Scott CareyDate: 2008-09-28 16:24:06
Subject: Re: Slow updates, poor IO
Previous:From: Scott MarloweDate: 2008-09-27 22:54:20
Subject: Re: Slow updates, poor IO

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