Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Reducing stats collection overhead
- From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: <pgsql-hackers(at)postgreSQL(dot)org>
- Subject: Re: Reducing stats collection overhead
- Date: Sun, 29 Apr 2007 12:14:21 +0100
- Message-id: <1177845261.3663.88.camel@silverbirch.site> <text/plain>
On Sun, 2007-04-29 at 00:44 -0400, Tom Lane wrote: > The first design that comes to mind is that at transaction end > (pgstat_report_tabstat() time) we send a stats message only if at least > X milliseconds have elapsed since we last sent one, where X is > PGSTAT_STAT_INTERVAL or closely related to it. We also make sure to > flush stats out before process exit. Sounds like a good general, long term solution. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
- References:
- Reducing stats collection overhead
- From: Tom Lane
- Reducing stats collection overhead
- Prev by Date: Re: Feature freeze progress report
- Next by Date: Re: Feature freeze progress report
- Previous by thread: Re: Reducing stats collection overhead
- Next by thread: Re: Reducing stats collection overhead
- Indexes: