From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_stat_statements temporary file |
Date: | 2012-05-25 16:52:51 |
Message-ID: | CABUevEzpL=nWM4sBLF7uY4xEpW8tDG2OgFF_MR+NyegbqAWATQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 25, 2012 at 6:49 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 5/25/12 8:19 AM, Tom Lane wrote:
>> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>>> On Friday, May 25, 2012 04:03:49 PM Peter Geoghegan wrote:
>>>> Where do you suggest the file be written to?
>>
>>> One could argue stats_temp_directory would be the correct place.
>>
>> No, that would be exactly the *wrong* place, because that directory can
>> be on a RAM disk. We need to put this somewhere where it'll survive
>> a shutdown.
>
> Mind you, I can imagine a busy system wanting to keep PSS on a ram disk
> as well. But users should be able to make that decision separately from
> the stats file.
Why would they want that? PSS only writes the tempfile on shutdown and
reads it on startup. Unlike pgstats which reads and writes it all the
time.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2012-05-25 16:54:46 | Re: pg_stat_statements temporary file |
Previous Message | Josh Berkus | 2012-05-25 16:49:51 | Re: pg_stat_statements temporary file |