Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 3D4439FB1CB; Sat, 13 Jan 2007 20:24:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 13749-08; Sat, 13 Jan 2007 20:24:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 08DCA9FB1BA; Sat, 13 Jan 2007 20:24:29 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l0E0OSSO028392; Sat, 13 Jan 2007 19:24:28 -0500 (EST) To: Jignesh Shah cc: pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: Performance of Parser? In-reply-to: <45A96D70.90506@sun.com> References: <45A96D70.90506@sun.com> Comments: In-reply-to Jignesh Shah message dated "Sat, 13 Jan 2007 23:38:24 +0000" Date: Sat, 13 Jan 2007 19:24:28 -0500 Message-ID: <28391.1168734268@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/215 X-Sequence-Number: 22816 Jignesh Shah writes: > The appserver is basically using bunch of prepared statements that the > server should be executing directly without doing the parsing again. Better have another look at that theory, because you're clearly spending a lot of time in parsing (operator resolution to be specific). I think your client code is failing to re-use prepared statements the way you think it is. regards, tom lane