From: Ray Stell <stellr@cns.vt.edu>
To: pgsql-performance@postgresql.org
Cc: Craig A. James <cjames@modgraph-usa.com>
Subject: Re: How to debug performance problems
Date: Wed, 21 Feb 2007 11:40:49 -0500
Message-ID: <20070221164049.GA14702@cns.vt.edu> (raw)
In-Reply-To: <45DC6ECD.9000705@modgraph-usa.com>
References: <Pine.LNX.4.62.0702191150020.15820@wr-linux02>
<45D9E646.6060909@modgraph-usa.com>
<20070221154520.GA25149@cns.vt.edu>
<45DC6ECD.9000705@modgraph-usa.com>
On Wed, Feb 21, 2007 at 08:09:49AM -0800, Craig A. James wrote:
> I hope I didn't give the impression that these were the only thing to look
> at ... those four items just popped into my head, because they've come up
> repeatedly in this forum. There are surely more things that could be
> suspect; perhaps others could add to your list.
I'm only clueless about the details of pg, not db perf concepts. Really,
a mechanism to determine where the system is spending the response
time is key. As you pointed out, the added table may not be the issue.
In fact, if you can't measure where the db time is being spent
you will be lucky to fix a performance issue, since you don't really
know what resources need to be addressed.
> so you have to dig in and find it yourself.
this afternoon, maybe.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: stellr@cns.vt.edu, cjames@modgraph-usa.com
Subject: Re: How to debug performance problems
In-Reply-To: <20070221164049.GA14702@cns.vt.edu>
* 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