From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dan Austin <DAustin@au.westfield.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pgstat.tmp file activity
Date: Thu, 22 Dec 2005 11:53:01 -0500
Message-ID: <23603.1135270381@sss.pgh.pa.us> (raw)
In-Reply-To: <ED242F3A9037824A952B71B480A5D7ED6DFAA4@ausyd-exmb01.au.ad.westfield.com>
References: <ED242F3A9037824A952B71B480A5D7ED6DFAA4@ausyd-exmb01.au.ad.westfield.com>
"Dan Austin" <DAustin@au.westfield.com> writes:
> Solaris 10 has a tool called dtrace which reveals that pid #687 (a
> postgres backend) is doing a LOT of writing to a single file (iosnoop.d
> for you dtrace hackers):
> UID PID D BLOCK SIZE COMM PATHNAME
> 103 687 W 120384 98304 postgres
> /export/data/pgsql/data/global/pgstat.tmp.687
Hmm. That's the stats collector creating a new current-stats file,
which it does every half second or so. You might think about disabling
stats collection if you don't have a need for it. But I'm having a hard
time believing that that's the main cause of your bottleneck. The
backends aren't supposed to block waiting for the stats collector ...
regards, tom lane
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: tgl@sss.pgh.pa.us, DAustin@au.westfield.com
Subject: Re: Pgstat.tmp file activity
In-Reply-To: <23603.1135270381@sss.pgh.pa.us>
References: <ED242F3A9037824A952B71B480A5D7ED6DFAA4@ausyd-exmb01.au.ad.westfield.com> <23603.1135270381@sss.pgh.pa.us>
* 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