From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Adi Alurkar <adi(at)sf(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Equivalent praxis to CLUSTERED INDEX? |
Date: | 2004-08-27 19:34:57 |
Message-ID: | 87acwgml26.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> but is there any significant performance benefit to doing that which would
> offset the compaction advantage?
Just as a side comment. Setting PCTFREE 0 PCTUSED 100 on tables that have no
updates on them has an astonishingly big effect on speed. So the penalty for
leaving some space free really is substantial.
I think the other poster is right. Oracle really needs pctfree because of the
way it handles updates. Postgres doesn't really need as much because it
doesn't try to squeeze the new tuple in the space the old one took up. If it
doesn't fit on the page the worst that happens is it has to store it on some
other page, whereas oracle has to do its strange row chaining thing.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-27 19:42:50 | Re: Equivalent praxis to CLUSTERED INDEX? |
Previous Message | Greg Stark | 2004-08-27 19:31:22 | Re: Equivalent praxis to CLUSTERED INDEX? |