Re: How much expensive are row level statistics?

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-performance(at)postgresql(dot)org>, "Carlos Benkendorf" <carlosbenkendorf(at)yahoo(dot)com(dot)br>
Subject: Re: How much expensive are row level statistics?
Date: 2005-12-16 14:40:39
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3417DDB39@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> Now there goes Tom with his skeptical eye again, and here comes me
> saying "oops" again. Further tests show that for this application

I made the same mistake, fwiw. The big hit comes with command_string.
However, row level stats bring a big enough penalty (~10% on my usage)
that I keep them turned off. The penalty is not just run time either,
but increased cpu time. It just isn't an essential feature so unless it
causes near zero extra load it will stay off on my servers.

Additionally, back when I was testing the win32/pg platform I was
getting random restarts of the stats collector when the server was under
high load and row_level stats were on. This was a while back so this
issue may or may not be resolved...it was really nasty because it
cleared out pg_stats_activity which in turn ruined my admin tools. I
should probably give that another look.

Merlin

Browse pgsql-performance by date

  From Date Subject
Next Message Jaime Casanova 2005-12-16 14:45:34 Re: Overriding the optimizer
Previous Message Csaba Nagy 2005-12-16 14:32:47 Re: Crashing DB or Server?