Re: Megabytes of stats saved after every connection

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Jeff Trout <threshar(at)torgo(dot)978(dot)org>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org>, pgsql-general(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: Megabytes of stats saved after every connection
Date: 2005-07-29 13:43:22
Message-ID: 20050729134321.GC13680@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jul 29, 2005 at 09:08:28AM -0400, Jeff Trout wrote:
>
> On Jul 28, 2005, at 2:40 PM, Jan Wieck wrote:
>
> >Then again, the stats file is only written. There is nothing that
> >actually forces the blocks out. On a busy system, one individual
> >stats file will be created, written to,
>
> If one is running with stats_reset_on_server_start true (the default)
> do we even need this file if it is never read?
>
> To help alleviate his problem could he symlink it to /dev/null?

If you don't want the stat collector to run, you can disable it. No
need to play games with a useless pgstat file.

Anyway -- I see this as an argument in favor of the ability to
deactivate stats on a per-database basis.

--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"The important things in the world are problems with society that we don't
understand at all. The machines will become more complicated but they won't
be more complicated than the societies that run them." (Freeman Dyson)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-07-29 13:55:18 Re: vacuum freeze
Previous Message Zlatko Matić 2005-07-29 13:30:49 templates, encoding