pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Huttley <John@mib-infotech.co.nz>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow updates, poor IO
Date: Sun, 28 Sep 2008 10:33:08 -0400
Message-ID: <6110.1222612388@sss.pgh.pa.us> (raw)
In-Reply-To: <48DEB4D4.1020100@mib-infotech.co.nz>
References: <48DBE587.3050406@mib-infotech.co.nz>
	<20080926131556.GA1005@commandprompt.com>
	<48DD6A4A.10209@mib-infotech.co.nz>
	<dcc563d10809270809g17938b7fvf28a3624028e0f3b@mail.gmail.com>
	<48DEB4D4.1020100@mib-infotech.co.nz>

John Huttley <John@mib-infotech.co.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

view thread (22+ messages)  latest in thread

Message-ID: <6110.1222612388@sss.pgh.pa.us>
Permalink:  ../6110.1222612388@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6110.1222612388@sss.pgh.pa.us

copy link · copy postgr.es

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, John@mib-infotech.co.nz, scott.marlowe@gmail.com
  Subject: Re: Slow updates, poor IO
  In-Reply-To: <6110.1222612388@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