Re: Equivalent praxis to CLUSTERED INDEX? - Mailing list pgsql-performance

From Tom Lane
Subject Re: Equivalent praxis to CLUSTERED INDEX?
Date
Msg-id 1082.1093630769@sss.pgh.pa.us
Whole thread Raw
In response to Re: Equivalent praxis to CLUSTERED INDEX?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Equivalent praxis to CLUSTERED INDEX?  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Equivalent praxis to CLUSTERED INDEX?
Next
From: Artimenko Igor
Date:
Subject: Why those queries do not utilize indexes?