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

From Tom Lane
Subject Re: New FSM allocation policy
Date
Msg-id 7138.1220026179@sss.pgh.pa.us
Whole thread Raw
In response to Re: New FSM allocation policy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: New FSM allocation policy  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Tom Lane wrote:
>> There may
>> be no very good way to do that without maintaining some shared state,
>> ie the last page handed out.

> We could put an extra field on the FSM root page. Hmm, it doesn't 
> actually need to be a single global field, so we could have a field like 
> that on every FSM page, for better concurrency.

Yeah, that would work, and it is only a hint so you needn't WAL-log
changing it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: New FSM allocation policy
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Remove all traces that suggest that a non-Bison yacc might be