Re: Maintaining cluster order on insert - Mailing list pgsql-patches

From Jaime Casanova
Subject Re: Maintaining cluster order on insert
Date
Msg-id c2d9e70e0706152148h7824eaafh499ba536eec82149@mail.gmail.com
Whole thread Raw
In response to Re: Maintaining cluster order on insert  ("Jim C. Nasby" <decibel@decibel.org>)
Responses Re: Maintaining cluster order on insert  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Maintaining cluster order on insert  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-patches
On 5/27/07, Jim C. Nasby <decibel@decibel.org> wrote:
> On Mon, May 21, 2007 at 10:48:59AM +0100, Heikki Linnakangas wrote:
> >
> > IOW it's working as designed. But maybe it's not the desired behavior.
> > Should we have a special case and always respect the fillfactor when
> > inserting to the last page of the heap?
>
> I think that would be following with least surprise.

What's the status of this patch? are we waiting an update?

AFAIU, it's not fair to say that the patch maintain cluster order...
it just try to keep similar rows on the same page if possible (it's
not the same thing)... if it can't then it simply insert at the last
page as usual but we have wasted time in the try...

so the real question is if there is any performance win on this...
have you some numbers?

another question: if the fillfactor is 100% then is a complete waste
of time to look for a suggested block. maybe we could check for that?

--
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

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Load Distributed Checkpoints, revised patch
Next
From: "Simon Riggs"
Date:
Subject: Re: Load Distributed Checkpoints, revised patch