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

Re: Effect of stopped status collector process

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Siddharth Shah <siddharth(dot)shah(at)elitecore(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Effect of stopped status collector process
Date: 2008-11-25 13:54:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
Siddharth Shah <siddharth(dot)shah(at)elitecore(dot)com> writes:
> I have found pgstat.stat file taking too much write hits.
> As my need to deploy on flash based storage. I don't want higher I/O's
> To stop status collector process I have change postmaster.c by removing 
> calls of pgstat.c
> Now every thing is working fine, Status collector process is not initiated ?

> Any drawbacks for not writing pgstat.stat ?

Autovacuum doesn't work ...

If you are willing to run a hand-hacked version then I'd suggest doing
your experimentation with CVS HEAD.  There are changes in place already
to reduce the stats file traffic.

			regards, tom lane

In response to


pgsql-general by date

Next:From: Alvaro HerreraDate: 2008-11-25 14:03:52
Subject: Re: Effect of stopped status collector process
Previous:From: Jeff MacDonaldDate: 2008-11-25 13:46:37
Subject: pg_get_serial_sequence Strangeness/Unreliable?

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