Re: Unexpected page allocation behavior on insert-only tables

Greg Stark <gsstark@mit.edu>

From: Greg Stark <gsstark@mit.edu>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Michael Renner <michael.renner@amd.co.at>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2010-05-31T05:09:49Z

Lists: pgsql-hackers

On Mon, May 31, 2010 at 3:42 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> note that at no time do we have any FSM
> data for the bid table:
>
>
> 3. After awhile, autovacuum notices all the insert activity and kicks
> off an autoanalyze on the bid table.  When committed, this forces a
> relcache flush for each other backend's relcache entry for "bid".
> In particular, the smgr targblock gets reset.

This is an analyze-only scan? Why does analyze need to issue a
relcache flush? Maybe we only need to issue one for an actual vacuum
which would also populate the fsm?


-- 
greg