pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Adi Alurkar <adi@sf.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Equivalent praxis to CLUSTERED INDEX?
Date: Fri, 27 Aug 2004 14:19:29 -0400
Message-ID: <1082.1093630769@sss.pgh.pa.us> (raw)
In-Reply-To: <200408271748.i7RHmfJ15766@candle.pha.pa.us>
References: <200408271748.i7RHmfJ15766@candle.pha.pa.us>

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Agreed.  What I am wondering is with our system where every update gets
> a new row, how would this help us?  I know we try to keep an update on
> the same row as the original, but is there any significant performance
> benefit to doing that which would offset the compaction advantage?

Because Oracle uses overwrite-in-place (undoing from an UNDO log on
transaction abort), while we always write a whole new row, it would take
much larger PCTFREE wastage to get a useful benefit in PG than it does
in Oracle.  That wastage translates directly into increased I/O costs,
so I'm a bit dubious that we should assume there is a win to be had here
just because Oracle offers the feature.

			regards, tom lane



view thread (41+ messages)  latest in thread

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

 · 

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, pgman@candle.pha.pa.us, adi@sf.net
  Subject: Re: Equivalent praxis to CLUSTERED INDEX?
  In-Reply-To: <1082.1093630769@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