Re: postgresql.conf runtime statistics default

From: Yann Michel <yann-postgresql(at)spline(dot)de>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: postgresql.conf runtime statistics default
Date: 2005-06-10 04:57:02
Message-ID: 20050610045702.GA19866@zoom.spline.inf.fu-berlin.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi,

On Thu, Jun 09, 2005 at 02:11:22PM +0100, Richard Huxton wrote:
> >
> >To my question: I found the parameter "stats_reset_on_server_start"
> >which is set to true by default. Why did you choose this (and not false)
> >and what are the impacts of changeing it to false? I mean, as long as I
> >understood it, each query or statements generates some statistic data
> >which is used by the optimizer (or anything equal) later on. So in my
> >oppinion, wouldn't it be better so set this parameter to false and to
> >enable a kind of a "startup reset_stats" option?
>
> This is administrator statistics (e.g. number of disk blocks read from
> this index) not planner statistics. You're right - it would be foolish
> to throw away planner stats.

So what is best to set this parameter to and when? As I read this
parameter is documented within the section "16.4.7.2. Query and Index
Statistics Collector" so I guess it is better to set it to false as
described above. Or am I wrong?

Regards,
Yann

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Steve Pollard 2005-06-10 06:03:17 Re: Importing from pg_dump slow, low Disk IO
Previous Message Junaili Lie 2005-06-10 01:30:37 Re: Help with rewriting query