From: | Mark Stosberg <mark(at)summersault(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to debug performance problems |
Date: | 2007-02-21 17:49:12 |
Message-ID: | eri0nl$23bu$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Stosberg | 2007-02-21 18:02:16 | How to avoid vacuuming a huge logging table |
Previous Message | Ray Stell | 2007-02-21 16:40:49 | Re: How to debug performance problems |