Re: Location for pgstat.stat - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Location for pgstat.stat
Date
Msg-id 486A8300.1000909@hagander.net
Whole thread Raw
In response to Re: Location for pgstat.stat  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Location for pgstat.stat  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> Tom Lane wrote:
>>> Hmm ... that would almost certainly result in the stats being lost over
>>> a system shutdown.  How much do we care?
> 
>> Only for those who put it on a ramdrive. The default, unless you
>> move/sync it off, would still be the same as it is today. While not
>> perfect, the performance difference of going to a ramdrive might easily
>> be enough to offset that in some cases, I think.
> 
> Well, what I was wondering about is whether it'd be worth adding logic
> to copy the file to/from a "safer" location at startup/shutdown.

Oh, I see. I should think more before I answer sometimes :-)

Not sure. I guess my own personal concern would be how badly is
autovacuum affected by having to start off a blank set of stats? Any
other uses I have I think are capable of dealing with reset-to-zero states.

//Magnus



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fairly serious bug induced by latest guc enum changes
Next
From: Alvaro Herrera
Date:
Subject: Re: Location for pgstat.stat