Re: Lock Management: Waiting on locks

From: Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Lock Management: Waiting on locks
Date: 2014-11-26 18:57:42
Message-ID: CALSLE1OtoqKK4i6LK3GpmF+SuKFZhaAKNhourZ5fL62jKp+Wgg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Bill !

On Wed, Nov 26, 2014 at 9:07 AM, Bill Moran <wmoran(at)potentialtech(dot)com>
wrote:

> In addition to what you're getting from that query, include the xact_start
> and
> state_change columns from pg_stat_activity. My guess is that your code is
> starting a transaction, then running a query, then processing the query
> results before committing the transaction. Since query locks are held for
> the duration of the transaction, this will cause the locks to be held for a
> long time if the processing step takes a while.
>

Actually each of this transaction is just single INSERT or single UPDATE
query.

> If that turns out not to be the problem, then you'll probably need to
> provide
> a bit more detail before anyone will be able to provide a better answer. I
> mean, I'm even guessing that it's an app making the queries.

Can you let me know what exact details should be provided here?

Regards...

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G Johnston 2014-11-26 19:07:01 Re: Range type bounds
Previous Message Adrian Klaver 2014-11-26 18:43:58 Range type bounds