Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-performance-owner+M49626=pgsql-performance-ar@postgresql.org>)
	id 1UNmyY-0004ju-HJ for pgsql-performance@arkaria.postgresql.org;
	Thu, 04 Apr 2013 16:25:22 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-performance-owner+M49626=pgsql-performance-ar@postgresql.org>)
	id 1UNmyX-0001P3-LB for pgsql-performance@arkaria.postgresql.org;
	Thu, 04 Apr 2013 16:25:21 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1UNmyW-0001Ox-MJ
	for pgsql-performance@postgresql.org; Thu, 04 Apr 2013 16:25:20 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1UNmyT-0005pT-9X
	for pgsql-performance@postgresql.org; Thu, 04 Apr 2013 16:25:20 +0000
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r34GPDTV018911;
	Thu, 4 Apr 2013 12:25:13 -0400 (EDT)
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Franck Routier <franck.routier@axege.com>
cc: Nikolas Everett <nik9000@gmail.com>,
	postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: What happens between end of explain analyze and end of query
	execution ?
In-reply-to: <515D9FC5.7030105@axege.com>
References: <515D92BF.5000309@axege.com>
	<CAPmjWd100eemBz1RTw=r24zgh8+YO8iq86fThqsALznrPuyWqg@mail.gmail.com>
	<515D9FC5.7030105@axege.com>
Comments: In-reply-to Franck Routier <franck.routier@axege.com>
	message dated "Thu, 04 Apr 2013 17:44:05 +0200"
Date: Thu, 04 Apr 2013 12:25:13 -0400
Message-ID: <18910.1365092713@sss.pgh.pa.us>
X-Pg-Spam-Score: -4.3 (----)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Franck Routier <franck.routier@axege.com> writes:
> Right, explain alone takes 3.6 seconds, so the time really seems to go 
> query planning...

Well, you've not shown us the query, so it's all going to be
speculation.  But maybe you have some extremely expensive function that
the planner is evaluating to fold to a constant, or something like that?
The generated plan isn't terribly complicated, but we can't see what
was required to produce it.

			regards, tom lane


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance