From: Dmitry Morozovsky <marck@rinet.ru>
To: Chris White (cjwhite) <cjwhite@cisco.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 7.4.5 file write issue
Date: Sat, 5 Mar 2005 12:29:02 +0300 (MSK)
Message-ID: <20050305122822.V83321@woozle.rinet.ru> (raw)
In-Reply-To: <200502222246.j1MMkDYO007021@sj-core-4.cisco.com>
References: <200502222246.j1MMkDYO007021@sj-core-4.cisco.com>
On Tue, 22 Feb 2005, Chris White (cjwhite) wrote:
CWc> We are noticing on our 7.4.5 system the following files are being written
CWc> approximately every 5 minutes
CWc>
CWc> /tmp/.s.PGSQL.5432
CWc> /tmp/.s.PGSQL.5432.lock
CWc>
CWc> Anybody know why they are being written? The reason I ask is because we are
CWc> running on a system that uses a laptop disk drive and requires at least 10
CWc> minutes idle time to spindown so it can recalibrate. This did not happen
CWc> when we were running 7.4.2, so does anybody have any idea what may have
CWc> changed between 7.4.2 and 7.4.5 to cause this to happen.
What about switching to memory-based /tmp ?
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: marck@rinet.ru, cjwhite@cisco.com
Subject: Re: 7.4.5 file write issue
In-Reply-To: <20050305122822.V83321@woozle.rinet.ru>
References: <200502222246.j1MMkDYO007021@sj-core-4.cisco.com> <20050305122822.V83321@woozle.rinet.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox