On Mon, 2012-07-23 at 11:09 -0400, Tom Lane wrote:
> Jim Vanns <james(dot)vanns(at)framestore(dot)com> writes:
> > We're seeing SELECT statements and even EXPLAIN (no ANAYLZE)
> > statements hang indefinitely until *something* (we don't know what)
> > releases some kind of resource or no longer becomes a massive bottle
> > neck. These are the symptoms.
> Does anything show up as blocked in the pg_locks view?
> Could you attach to the stuck process with gdb and get a stack trace?
Haven't been quite brave enough to do that yet - this is a production
server. I did manage to strace a process though - it (the server side
process of a psql EXPLAIN) appeared to spin on an awful lot of semop()
calls with the occasional read(). Of course, in the context of a shared
memory system such as postgres I'd expect to see quite a lot of semop()
calls but I've no idea how much is normal and how much is excessive.
> regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Robert Haas||Date: 2012-07-23 19:07:10|
|Subject: Re: postgres clustering interactions with pg_dump|
|Previous:||From: Tom Lane||Date: 2012-07-23 15:09:16|
|Subject: Re: Odd blocking (or massively latent) issue - even with EXPLAIN|