Re: Megabytes of stats saved after every connection

From: Jeff Trout <threshar(at)torgo(dot)978(dot)org>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: 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:08:28
Message-ID: F5F5D23D-B1F8-43F9-8C8E-83F47099A302@torgo.978.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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?

--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Zlatko Matić 2005-07-29 13:30:49 templates, encoding
Previous Message Randall Perry 2005-07-29 12:58:11 Re: Rules vs Triggers