Tom Lane wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> > Well, if you issue a manual vacuum then you can argue that it has been
> > "modified" (it's seeing some activity). But immediately after a vacuum
> > the table will not be vacuumed by autovac if there's no other activity,
> > because there's no need for it, so we can create the entry anyway and it
> > won't make an immediate difference.
>
> You're ignoring the point of this thread, which is that creating
> hashtable entries for tables that aren't actively being modified
> causes significant ongoing overhead that we ought to try to minimize.
True. I agree with the rest of the reasoning in this case.
Maybe the fact that the stat file is completely rewritten every 500 ms
should be reconsidered, if in the future someone chooses to rewrite
the stat system. We can reconsider this part then, as well.
--
Alvaro Herrera http://www.PlanetPostgreSQL.org
Jason Tesser: You might not have understood me or I am not understanding you.
Paul Thomas: It feels like we're 2 people divided by a common language...
