From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim Vanns <james.vanns@framestore.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Odd blocking (or massively latent) issue - even with EXPLAIN
Date: Mon, 23 Jul 2012 11:09:16 -0400
Message-ID: <29948.1343056156@sss.pgh.pa.us> (raw)
In-Reply-To: <1343032905.12579.3.camel@sys367.ldn.framestore.com>
References: <1343032905.12579.3.camel@sys367.ldn.framestore.com>
Jim Vanns <james.vanns@framestore.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?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, james.vanns@framestore.com
Subject: Re: Odd blocking (or massively latent) issue - even with EXPLAIN
In-Reply-To: <29948.1343056156@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox