Re: "slow" queries

From: Tim Bunce
Subject: Re: "slow" queries
Date: ,
Msg-id: 20090302212433.GX8731@timac.local
(view: Whole thread, Raw)
In response to: Re: "slow" queries  (Tom Lane)
Responses: Re: "slow" queries  (Scott Marlowe)
List: pgsql-performance

Tree view

"slow" queries  (Brian Cox, )
 Re: "slow" queries  (Robert Haas, )
 Re: "slow" queries  (Tom Lane, )
 Re: "slow" queries  ("Cox, Brian", )
  Re: "slow" queries  (Tom Lane, )
 Re: "slow" queries  (Brian Cox, )
  Re: "slow" queries  (Scott Carey, )
  Re: "slow" queries  (Robert Haas, )
  Re: "slow" queries  (Tom Lane, )
   Re: "slow" queries  (Tim Bunce, )
    Re: "slow" queries  (Scott Marlowe, )
 Re: "slow" queries  (Brian Cox, )
  Re: "slow" queries  (Tom Lane, )
 Re: "slow" queries  (Brian Cox, )

On Mon, Mar 02, 2009 at 02:29:31PM -0500, Tom Lane wrote:
> Brian Cox <> writes:
> > select locktype,database,relation,virtualxid,virtualtransaction,pid,mode
> > from pg_locks order by mode;
>
> If you hadn't left out the "granted" column we could be more sure,
> but what it looks like to me is the DROP (pid 13842) is stuck behind
> the <IDLE> transaction (pid 13833).  In particular these two rows of
> pg_locks look like a possible conflict:
>
> >   relation      | 26472437 | 26472508 |            | 15/69749
> > | 13842 | AccessExclusiveLock
>
> >   relation      | 26472437 | 26472508 |            | 11/131
> > | 13833 | AccessShareLock

Would it be possible to write a stored procedure that would read
pg_locks, and other relevant tables, and list what's blocking what
in a simplified form?

Tim.


pgsql-performance by date:

From: Tom Lane
Date:
Subject: Re: Postgres 8.3, four times slower queries?
From: Hans Liebenberg
Date:
Subject: Substring search using "exists" with a space in the search term