Re: Effect of stopped status collector process - Mailing list pgsql-general

From Merlin Moncure
Subject Re: Effect of stopped status collector process
Date
Msg-id b42b73150811251837xb23b201w22021224550f5e26@mail.gmail.com
Whole thread Raw
In response to Re: Effect of stopped status collector process  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Effect of stopped status collector process
List pgsql-general
On Tue, Nov 25, 2008 at 9:03 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Tom Lane wrote:
>
>> 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.
>
> Why do we _have_ to write the file to disk?  I wonder if it would work
> to store the file in a mmaped memory region and have the readers get
> data from there.  We could have more than one copy, reference-counted so
> that they can be removed when the old readers are gone.

what about fifo files...would they be appropriate for something like this?

merlin

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Question about anyelement datatype
Next
From: "John Smith"
Date:
Subject: slow, long-running 'commit prepared'