From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kyle <kaf(at)nwlink(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: poor performance on 7.1 vs 7.0 |
Date: | 2001-05-08 21:53:30 |
Message-ID: | 8690.989358810@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Kyle <kaf(at)nwlink(dot)com> writes:
> When I profile the postmaster do the forked backends also show up in
> the profile? Or do I need to profile those separately? (and how?)
As each process (postmaster or backend) terminates, it drops a gmon.out
file in the directory it was working in. As long as you are profiling
a backend that's alone in the database it's in, the gmon.out file in
$PGDATA/base/dbnumber/gmon.out is the one you want.
The profile results for a backend will include the CPU usage of the
postmaster up to the instant that the backend was forked off, but it's
normally easy to ignore that, particularly if you haven't been running
the profilable postmaster for very long before you do the test.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fran Fabrizio | 2001-05-08 21:54:07 | Re: select off of a view going slowly |
Previous Message | Peter Eisentraut | 2001-05-08 21:21:51 | Re: ALTER COLUMN |