Skip site navigation (1) Skip section navigation (2)

Re: measure database contention

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: "psql performance list" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: measure database contention
Date: 2008-12-17 14:49:26
Message-ID: b42b73150812170649rd0a689bw41b8215d8488f9b4@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Tue, Dec 16, 2008 at 2:32 PM, Jaime Casanova
<jcasanov(at)systemguards(dot)com(dot)ec> wrote:
> Hi,
>
> we have a some bad queries (developers are working on that), some of
> them run in 17 secs and that is the average but when analyzing logs i
> found that from time to time some of them took upto 3 mins (the same
> query that normally runs in 17secs).
>
> so my question is: how could i look for contention problems?

Sometimes queries can have fluctuating plans.  For example this can
happen if you have sorts or hashes that are very near the allowed
limit set in work_mem.  so you want to catch it both ways via explain
analyze.

merlin

In response to

pgsql-performance by date

Next:From: Jaime CasanovaDate: 2008-12-17 15:22:04
Subject: Re: measure database contention
Previous:From: Robert HaasDate: 2008-12-17 14:18:54
Subject: Re: measure database contention

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group