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

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)surnet(dot)cl>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Federico Di Gregorio <fog(at)initd(dot)org>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector
Date: 2005-06-28 02:39:55
Message-ID: 2156.1119926395@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
Alvaro Herrera <alvherre(at)surnet(dot)cl> writes:
> What about arranging postmaster's main loop so that it starts the stats
> collector process if one of the options is activated (assuming they were
> all off at start)?  Right now you have to restart the server, but I
> don't see why it has to be like that.

Actually, this entire thread is based on a misconception: the "bug"
reporter was under the misimpression that the sum total of what the
collector does is described by the three suboptions, and so having
start_collector on without any of the suboptions on is a useless state.
But this is not so.  The collector tracks backend start/end in any case,
and so you get a useful list of sessions in pg_stat_activity even
without enabling any of the more expensive reporting options.

So my vote at this point is that the code is not broken and we should
not change it.  Possibly the documentation could stand a little
improvement.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-06-28 06:05:33
Subject: Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector
Previous:From: satish reddyDate: 2005-06-28 01:35:38
Subject: Reg No Error Information Available

pgsql-patches by date

Next:From: Michael FuhrDate: 2005-06-28 02:49:18
Subject: Re: Performance analysis of plpgsql code
Previous:From: Karl O. PincDate: 2005-06-28 01:54:08
Subject: Re: Performance analysis of plpgsql code

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