Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 0344664FDAB for ; Fri, 12 Dec 2008 07:53:30 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 49034-03; Fri, 12 Dec 2008 07:53:23 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by mail.postgresql.org (Postfix) with ESMTP id C417064FD91; Fri, 12 Dec 2008 07:53:21 -0400 (AST) Received: from feivel (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 0B4DB214E67; Fri, 12 Dec 2008 12:53:15 +0100 (CET) Received: by feivel (Postfix, from userid 1000) id 7854DD6D2E; Fri, 12 Dec 2008 12:53:14 +0100 (CET) Date: Fri, 12 Dec 2008 12:53:14 +0100 From: Michael Meskes To: "Haszlakiewicz, Eric" Cc: Michael Meskes , pgsql-interfaces@postgresql.org Subject: Re: deallocating prepared statements Message-ID: <20081212115314.GA24477@feivel.credativ.de> Mail-Followup-To: "Haszlakiewicz, Eric" , Michael Meskes , pgsql-interfaces@postgresql.org References: <9D29FD18CBD74A478CBA86E6EF6DBAD402FF8CC9@CHI4EVS04.corp.transunion.com> <20081203141255.GA1874@feivel.credativ.de> <9D29FD18CBD74A478CBA86E6EF6DBAD40308029E@CHI4EVS04.corp.transunion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9D29FD18CBD74A478CBA86E6EF6DBAD40308029E@CHI4EVS04.corp.transunion.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/15 X-Sequence-Number: 6832 [Sorry, I seem to not have answered yet, I thought I had. ] On Wed, Dec 03, 2008 at 11:38:27AM -0600, Haszlakiewicz, Eric wrote: > So why is preparing a statement in ecpg different from preparing one > with libpq? Isn't the actual prepare done on the server? The actual prepare yes, but there are internal ecpg structures involved too, e.g. it needs the connection involved. Without getting the connection information there is no way to deallocate the statement. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!