From: Mark Stosberg <mark@summersault.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to debug performance problems
Date: Wed, 21 Feb 2007 12:49:12 -0500
Message-ID: <eri0nl$23bu$1@news.hub.org> (raw)
In-Reply-To: <20070221154520.GA25149@cns.vt.edu>
References: <Pine.LNX.4.62.0702191150020.15820@wr-linux02>
<45D9E646.6060909@modgraph-usa.com>
<20070221154520.GA25149@cns.vt.edu>
Ray Stell wrote:
> I'd like to have a toolbox prepared for when performance goes south.
> I'm clueless. Would someone mind providing some detail about how to
> measure these four items Craig listed:
>
> 1. The first thing is to find out which query is taking a lot of time.
>
> 2. A long-running transaction keeps vacuum from working.
>
> 3. A table grows just enough to pass a threshold in the
> planner and a drastically different plan is generated.
I just ran into a variation of this:
3.5 A table grows so large so that VACUUMING it takes extremely long,
interfering with the general performance of the system.
In our case, we think the table had about 36 million rows when it hit
that threshold.
I'm now working on a better solution for that table.
Mark
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: mark@summersault.com
Subject: Re: How to debug performance problems
In-Reply-To: <eri0nl$23bu$1@news.hub.org>
* 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