Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 058901FBF225 for ; Tue, 27 Dec 2011 10:21:19 -0400 (AST) Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RfXty-0000nY-QI for pgsql-performance@postgresql.org; Tue, 27 Dec 2011 14:21:18 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RfXtm-0001qJ-C6 for pgsql-performance@postgresql.org; Tue, 27 Dec 2011 06:21:02 -0800 Date: Tue, 27 Dec 2011 06:21:02 -0800 (PST) From: MirrorX To: pgsql-performance@postgresql.org Message-ID: <1324995662366-5103182.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.0 (/) X-Archive-Number: 201112/173 X-Sequence-Number: 45972 i am not using prepared statements for now :) i just said that probably, if i do use them, i will get rid of that extra time since the plan will be already 'decided' in advance -- View this message in context: http://postgresql.1045698.n5.nabble.com/parse-bind-take-more-time-than-execute-tp5102940p5103182.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.