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

Re: BUG #1707: statistics collector starts with stats_start_collector = false

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Federico Di Gregorio <fog(at)initd(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1707: statistics collector starts with stats_start_collector = false
Date: 2005-06-13 04:39:14
Message-ID: 11312.1118637554@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> I don't have a problem with removing it as a writable option ... but
>> I'm thinking we should leave it as a read-only GUC parameter (like
>> the several others we have already).  Otherwise we'll need to add some
>> other method of finding out whether the collector is running.

> Why would a user care?

luser> It's not collecting statistics!

us> Is the collector running?

luser> How should I know?

us> er ...

If we don't have a way to check this, we'll regret it soon enough...
now maybe a GUC setting isn't the optimal way, but I think we need
*some* way besides ps.  ps doesn't work remotely and I think there's
no simple equivalent under Windows either.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Achilleus MantziosDate: 2005-06-13 06:59:03
Subject: Re: BUG #1715: dbmirror replaces nextval, setval functions
Previous:From: Bruce MomjianDate: 2005-06-13 04:31:02
Subject: Re: BUG #1707: statistics collector starts with stats_start_collector

pgsql-patches by date

Next:From: Pavel StehuleDate: 2005-06-13 05:07:39
Subject: plpgsql raise - parameters can be expressions
Previous:From: Bruce MomjianDate: 2005-06-13 04:31:02
Subject: Re: BUG #1707: statistics collector starts with stats_start_collector

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