Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 61FD41FBF225 for ; Tue, 27 Dec 2011 09:34:42 -0400 (AST) Received: from sam.nabble.com ([216.139.236.26]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RfXAu-0002yt-Nq for pgsql-performance@postgresql.org; Tue, 27 Dec 2011 13:34:41 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RfXAh-000650-Ej for pgsql-performance@postgresql.org; Tue, 27 Dec 2011 05:34:27 -0800 Date: Tue, 27 Dec 2011 05:34:27 -0800 (PST) From: MirrorX To: pgsql-performance@postgresql.org Message-ID: <1324992867448-5103116.post@n5.nabble.com> In-Reply-To: References: <1324983133749-5102940.post@n5.nabble.com> Subject: Re: parse - bind take more time than execute MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.9 (/) X-Archive-Number: 201112/171 X-Sequence-Number: 45970 thx a lot for your answer :) 2) default_statistics_target is set to (default) 100 and there no special statistics per-column 3) i will do that very soon 4) in absolute units i can see the same query having similar stats to these: parse -> 600 ms bind -> 300 ms execute -> 50 ms the query mentioned above is a simple select from one table using using two where conditions. and this table has 1 additional index (except the primary key) on the columns that are part of the where clause -- View this message in context: http://postgresql.1045698.n5.nabble.com/parse-bind-take-more-time-than-execute-tp5102940p5103116.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.