From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, "Bruce Momjian" <bruce(at)momjian(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Maintaining cluster order on insert |
Date: | 2007-05-18 04:53:52 |
Message-ID: | c2d9e70e0705172153g3207adb6kd4abdfdf3a9215ff@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On 5/16/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)com> wrote:
> Jim C. Nasby wrote:
> > What about adding the ability to ask the FSM for a page that's near a
> > given page? That way if you did have to go to the FSM you could at least
> > try and insert close to the page you originally wanted.
>
> Yeah, there's always room for improvement. I made the patch when I was
> working on clustered indexes, and was mostly concerned about getting
> inserts to the same page as other tuples with similar values so that the
> clustered index stays clustered.
>
the patch doesn't apply in cvs... you'll need to update it...
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2007-05-18 04:54:34 | Re: Maintaining cluster order on insert |
Previous Message | Atul Deopujari | 2007-05-18 03:47:25 | Re: Planning large IN lists |
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2007-05-18 04:54:34 | Re: Maintaining cluster order on insert |
Previous Message | Jaime Casanova | 2007-05-18 04:28:34 | Re: Updateable cursors patch |