From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dan Austin" <DAustin(at)au(dot)westfield(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Pgstat.tmp file activity |
Date: | 2005-12-23 06:00:39 |
Message-ID: | 16595.1135317639@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Dan Austin" <DAustin(at)au(dot)westfield(dot)com> writes:
> 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.
OK, so the stats collector is off the hook: it's not writing anything
in that directory. I'd say you have a pretty conventional
query-optimization problem here after all --- you want to cut the
traffic into those temp files. You ought to be looking at EXPLAIN
ANALYZE info for your common queries.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mohamed Fazil | 2005-12-23 06:02:31 | Re: How to implement PGSQL8.0 no-installer in Windows 2k,XP & NT ? |
Previous Message | Dan Austin | 2005-12-23 05:50:32 | Re: Pgstat.tmp file activity |