Subject: Re: Odd blocking (or massively latent) issue - even with
 EXPLAIN
From: Jim Vanns <james.vanns@framestore.com>
To: Craig Ringer <ringerc@ringerc.id.au>
Cc: Jim Vanns <james.vanns@framestore.com>,
	Martin French <Martin.French@romaxtech.com>,
	pgsql-performance@postgresql.org, pgsql-performance-owner@postgresql.org
In-Reply-To: <500DEC9E.90603@ringerc.id.au>
References: <1343032905.12579.3.camel@sys367.ldn.framestore.com>
	<OF4731D4BD.B722B5CE-ON80257A44.004B3A30-80257A44.004BABD3@LocalDomain>
	<1343054763.12579.110.camel@sys367.ldn.framestore.com>
	<500DEC9E.90603@ringerc.id.au>
Content-Type: text/plain; charset="UTF-8"
Organization: Framestore
Date: Tue, 24 Jul 2012 09:37:12 +0100
Message-ID: <1343119032.12579.140.camel@sys367.ldn.framestore.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2012-07-24 at 08:30 +0800, Craig Ringer wrote:
> On 07/23/2012 10:46 PM, Jim Vanns wrote:
> > Nothing obvious - and we log a fair amount. No tmp table creations,
> > no locks held.
> >
> > To add to this EXPLAIN reports it took only 0.23ms to run (for example)
> > whereas the wall clock time is more like 20-30 minutes (or up to n hours
> > as I said where everything appears to click back into place at the same
> > time).
> How many concurrent connections do you have?

Between 4 and 64 at peak! max_connections is only set to 100.

Jim

> --
> Craig Ringer

-- 
Jim Vanns
Systems Programmer
Framestore