| Author |
BUG #1707: statistics collector starts with stats_start_collector = false
|
|
| Federico Di Gregorio 2005-06-12, 1:23 pm |
|
The following bug has been logged online:
Bug reference: 1707
Logged by: Federico Di Gregorio
Email address: fog@initd.org
PostgreSQL version: 7.4.8
Operating system: Debian GNU/Linux
Description: statistics collector starts with stats_start_collecto
r =
false
Details:
If the following combinatio of parameters is used:
stats_start_collecto
r = false
stats_row_level = true
the collector process is started even if the documentation says that "The
parameter stats_start_collecto
r must be set to true for the statistics
collector to be launched at all."
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
| |
| Tom Lane 2005-06-12, 8:24 pm |
| "Federico Di Gregorio" <fog@initd.org> writes:
> If the following combinatio of parameters is used:
> stats_start_collecto
r = false
> stats_row_level = true
> the collector process is started even if the documentation says that "The
> parameter stats_start_collecto
r must be set to true for the statistics
> collector to be launched at all."
I believe stats_start_collecto
r is forced on if any of the subsidiary
parameters is set. Isn't that what you want?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
| |
| Tom Lane 2005-06-13, 3:24 am |
| Bruce Momjian <pgman@candle.pha.pa.us> writes:
> If that is the logic, why do we have stats_start_collecto
r at all?
Ask Jan ;-)
I can see some advantage to it as a way of finding out whether the
collector was started or not ... but if that's the intent, we
should make it non user-writable.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
| |
| Tom Lane 2005-06-13, 3:24 am |
| Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I can see someone turning it off but leaving other options on because
> they will want to turn them on later.
"later" when? It's not useful to try to turn on stats_start_collecto
r
after postmaster start, because the UDP socket won't exist.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
| |
| Tom Lane 2005-06-13, 3:24 am |
| Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Later such as in a later postmaster start, but personally I would just
> remove the option completely.
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.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql
.org
| |
| Tom Lane 2005-06-13, 3:24 am |
| Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
[color=darkred]
> 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
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
|
|
|
|