Re: Unexpected page allocation behavior on insert-only tables - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Unexpected page allocation behavior on insert-only tables
Date
Msg-id AANLkTill9sP47NQyVuuEz4UICUcfY1aQJrDUXPVmoA1t@mail.gmail.com
Whole thread Raw
In response to Re: Unexpected page allocation behavior on insert-only tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unexpected page allocation behavior on insert-only tables
List pgsql-hackers
On Sun, May 30, 2010 at 10:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> pretty clear what is going on.  See the logic in
> RelationGetBufferForTuple, and note that at no time do we have any FSM
> data for the bid table:

Is this because, in the absence of updates or deletes, we never vacuum it?

> 4. Now, all the backends again decide to try to insert into the last
> available block.  So everybody jams into the partly-filled block 10,
> until it gets filled.

Would it be (a) feasible and (b) useful to inject some entropy into this step?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unexpected page allocation behavior on insert-only tables
Next
From: Takahiro Itagaki
Date:
Subject: Re: Unexpected page allocation behavior on insert-only tables