pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Dan Austin <DAustin@au.westfield.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pgstat.tmp file activity
Date: Tue, 27 Dec 2005 15:08:44 -0600
Message-ID: <20051227210844.GP72143@pervasive.com> (raw)
In-Reply-To: <ED242F3A9037824A952B71B480A5D7ED6DFAD1@ausyd-exmb01.au.ad.westfield.com>
References: <ED242F3A9037824A952B71B480A5D7ED6DFAD1@ausyd-exmb01.au.ad.westfield.com>

On Fri, Dec 23, 2005 at 04:50:32PM +1100, Dan Austin wrote:
> > [...]
> > Right, the file is fully written under a temp name, and then 
> > rename()'d
> 
> This makes sense and is almost certainly not the cause of the problem.
> Although there is a lot more data being written to that file than I
> would have thought.
> 
> One of Sun's kernel engineers has come up with a solution that seems to
> have fixed the problem. Instead of increasing work_mem (which we still
> might do) we've mounted a swapfs partition over the pg temp directory:
> 
>   # mount | grep pgsql_tmp
>   /export/data/pgsql/data/base/64920741/pgsql_tmp on swap [...]
> 
> This has actually reduced the disk activity considerably. So far, the
> blocking problem seems to have gone.
> 
> Now to find some Postgres DBAs in Sydney to do some review / tuning of
> our memory settings. :-)

Note also that Solaris by default limits the amount of memory used for
disk caching, which is Not Good for PostgreSQL. IIRC this can be changed
with a sysctl, but I don't recall the details off-hand.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (10+ messages)  latest in thread

Message-ID: <20051227210844.GP72143@pervasive.com>
Permalink:  ../20051227210844.GP72143@pervasive.com/
Also on:    postgresql.org/message-id/20051227210844.GP72143@pervasive.com

 · 

reply

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: jnasby@pervasive.com, DAustin@au.westfield.com, tgl@sss.pgh.pa.us
  Subject: Re: Pgstat.tmp file activity
  In-Reply-To: <20051227210844.GP72143@pervasive.com>
  References: <ED242F3A9037824A952B71B480A5D7ED6DFAD1@ausyd-exmb01.au.ad.westfield.com> <20051227210844.GP72143@pervasive.com>

* 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