Re: lock contention, need profiling idea

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: AI Rumman <rummandba(at)gmail(dot)com>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: lock contention, need profiling idea
Date: 2014-07-01 18:39:43
Message-ID: CAHyXU0zUg_edYgtMFxH9GyHpCQ508hmevjpFxtaEVJJtWmP1eA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 30, 2014 at 5:36 PM, AI Rumman <rummandba(at)gmail(dot)com> wrote:
> I see lots of similar log message at a certain time in a day on Postgresql
> 9,.1:
>
> LOG: process 18855 still waiting for ShareLock on transaction 2856146023
> after 1001.209 ms
> STATEMENT: UPDATE table1 SET time = $1 WHERE id = $2
>
> The table1 size is 17 G.
>
> What could be the reason for this lock contention?
> autovacuum?
>
> Please give some idea.

Query pg_stat_activity and pg_locks on intervals and you'll get to the
bottom of this.

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jerry Sievers 2014-07-01 18:54:11 Re: Best way to list a roles owned objects?
Previous Message Jerry Sievers 2014-07-01 18:31:54 Re: Best way to list a roles owned objects?