X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 8BF88313877; Tue, 10 Jun 2003 04:50:42 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 23201-10; Tue, 10 Jun 2003 01:50:32 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 900DB30EDF2; Mon, 9 Jun 2003 15:47:01 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h59FkwU6017645; Mon, 9 Jun 2003 11:46:58 -0400 (EDT) To: Jonathan Gardner Cc: pgsql-interfaces@postgreSQL.org, pgsql-hackers@postgreSQL.org Subject: Re: Some quick notes about extending libpq for new protocol In-reply-to: <200306090842.26352.jgardner@jonathangardner.net> References: <9481.1054574376@sss.pgh.pa.us> <200306090842.26352.jgardner@jonathangardner.net> Comments: In-reply-to Jonathan Gardner message dated "Mon, 09 Jun 2003 08:42:25 -0700" Date: Mon, 09 Jun 2003 11:46:57 -0400 Message-ID: <17644.1055173617@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/25 X-Sequence-Number: 4236 Jonathan Gardner writes: > I'll admit -- the current state of PQfn is practically unuseable. However, the > idea is pretty cool. I think it would be nice to have a direct function call > mechanism that bypasses the parser. The ability to prepare a "SELECT foo($1, $2, ...)" statement pretty much eliminates any performance advantage that PQfn once had. While I've not had the opportunity to do performance tests, I'd think that a binary BIND and EXECUTE of such a statement would be about on a par with FunctionCall. regards, tom lane