Re: Potential autovacuum optimization: new tables - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Potential autovacuum optimization: new tables
Date
Msg-id CAM-w4HNj2Esz0ST=3uTy3QB8sFBZApU54eZOGX=Syd3gjm79_Q@mail.gmail.com
Whole thread Raw
In response to Re: Potential autovacuum optimization: new tables  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Potential autovacuum optimization: new tables  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Sat, Oct 13, 2012 at 3:13 AM, Stephen Frost <sfrost@snowman.net> wrote:
> Josh's concern is about autovacuum causing lots of stats churn, which is
> understandable, we don't want it constantly rescanning a table

I don't think rescanning the table is a big concern. autovacuum will
only scan as often as it feels like in the first place and these are
by definition small tables anyways.

Josh's stated concern was about the churn in the stats table. That
could cause extra vacuums on the stats table which could be a fairly
substantial table. Hopefully HOT updates and the visibility bitmap
would protect against that being too bad though.



-- 
greg



pgsql-hackers by date:

Previous
From: Gilles Darold
Date:
Subject: Re: pg_dump restore error
Next
From: Greg Stark
Date:
Subject: Re: Deprecating RULES