Effect of stopped status collector process

From: Siddharth Shah <siddharth(dot)shah(at)elitecore(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Effect of stopped status collector process
Date: 2008-11-25 13:44:18
Message-ID: 492C0132.6030501@elitecore.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

I have started to explore PG,
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 ?
Is there another way to achieve this or
Will this create any problem like If pgstat.c is initiating some data
structures
which is shared to postmaster.c or else part

- Siddharth.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff MacDonald 2008-11-25 13:46:37 pg_get_serial_sequence Strangeness/Unreliable?
Previous Message Tom Lane 2008-11-25 13:19:40 Re: Place of subselect