Re: "slow" queries

From: Tom Lane
Subject: Re: "slow" queries
Date: ,
Msg-id: 22227.1236022171@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: "slow" queries  (Brian Cox)
Responses: Re: "slow" queries  (Tim Bunce)
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, )

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

            regards, tom lane


pgsql-performance by date:

From: Aaron Guyon
Date:
Subject: Postgres 8.3, four times slower queries?
From: Tom Lane
Date:
Subject: Re: Postgres 8.3, four times slower queries?