Re: New FSM allocation policy - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: New FSM allocation policy
Date
Msg-id 1220286426.4371.176.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: New FSM allocation policy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, 2008-08-29 at 18:55 +0300, Heikki Linnakangas wrote:
> Tom Lane wrote:
> > Gregory Stark <stark@enterprisedb.com> writes:
> >> One idea, we could scan the rest of the current page and use the first match.
> > 
> >> Another, given the way your tree structure works you can also descend the tree
> >> with a "target" page. You can find the first page with enough free space after
> >> the target page if there are any. (Take left branch if it's > target and has
> >> enough free space else take right branch if there's enough free space else
> >> take left branch).
> > 
> > I think the trick here is how to also preserve the property that
> > different backends tend to be inserting into different pages. 
> 
> Yep. If we just always look at the next page, there's the danger of 
> having multiple backends compete for the same pages again.

Can the FSM hand out page ranges? That way we would be able to use the
next page logic without fear of competition.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: statement_cost_limit for regression testing.
Next
From: "Ryan Bradetich"
Date:
Subject: Re: Question regarding the database page layout.