Skip site navigation (1) Skip section navigation (2)

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: 2007-04-29 11:14:21
Message-ID: 1177845261.3663.88.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-hackers
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



In response to

pgsql-hackers by date

Next:From: Stefan KaltenbrunnerDate: 2007-04-29 11:36:00
Subject: Re: Feature freeze progress report
Previous:From: Martijn van OosterhoutDate: 2007-04-29 10:25:17
Subject: Re: question for serial types with CHECK conditions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group