Re: No heap lookups on index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, David Scott <davids(at)apptechsys(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: No heap lookups on index
Date: 2006-01-19 01:32:40
Message-ID: 6082.1137634360@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> Would this open the door for allowing tables to be maintained in CLUSTER
> order (at least at the block level if not within the blocks)? Though I
> have no idea how you'd handle page splits without a lot of pain

I think the way you'd attack that is by building the table with a pretty
low fill factor, so that there's room on each page for a number of
updates before you have to split. Since the index AM is going to be
dictating space allocation, this is all in its hands.

The existing CLUSTER code would probably be totally inapplicable to
this sort of organization --- we'd have to provide some alternate code
path for index-organized heaps.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dann Corbit 2006-01-19 01:34:20 Re: FW: Surrogate keys (Was: enums)
Previous Message Jim C. Nasby 2006-01-19 01:27:15 Re: No heap lookups on index

Browse pgsql-hackers by date

  From Date Subject
Next Message Dann Corbit 2006-01-19 01:34:20 Re: FW: Surrogate keys (Was: enums)
Previous Message Jim C. Nasby 2006-01-19 01:27:15 Re: No heap lookups on index