On Fri, 2003-09-12 at 13:06, Tom Lane wrote:
> > I can hardwire in something to hedge this off like setting the threshold
> > for shared tables much much lower than normal thresholds. I could also
> > do something more complicated and try to aggregate all the activity seen
> > by all the databases and when the sum exceeds the threshold then have
> > then perform a vacuum from template1 and analyze from all other
> > databases.
>
> That seems like more work than it's worth for a short-term stopgap.
>
> If Jan concludes that fixing pgstats is *really* hard and will not
> happen for awhile, then we could talk about more extensive workarounds
> in pg_autovacuum, but right now I doubt it's needed.
OK, I'll hold for now. The patches I just submitted should be fine, and
if the stats system doesn't get fixed, I'll make the small change where
vacuum is done from all databases, not just template1.
Thanks