Itagaki Takahiro wrote: <blockquote cite="mid:20091207100104.950F.52131E4D@oss.ntt.co.jp" type="cite"><pre
wrap="">GregSmith <a class="moz-txt-link-rfc2396E" href="mailto:greg@2ndquadrant.com"><greg@2ndquadrant.com></a>
wrote:
</pre><blockquote type="cite"><pre wrap="">I'm thinking that I should rename this new function
to pg_stat_reset_bgwriter so it's obvious how limited its target is. </pre></blockquote><pre wrap="">
I don't think it is a good name because we might have another cluster-level
statictics not related with bgwriter in the future. I hope you will suggest
"extensible" method when you improve this area. </pre></blockquote> I follow what you mean now. I'll take a look at
allowingpg_stat_reset to act on an input as you suggested, rather than adding more of these UDFs for every time
somebodyadds a new area they want to target clearing.<br /><br /><pre class="moz-signature" cols="72">--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
<a class="moz-txt-link-abbreviated" href="mailto:greg@2ndQuadrant.com">greg@2ndQuadrant.com</a> <a
class="moz-txt-link-abbreviated"href="http://www.2ndQuadrant.com">www.2ndQuadrant.com</a>
</pre>