From: Michael Meskes <meskes@postgresql.org>
To: Haszlakiewicz, Eric <EHASZLA@transunion.com>
Cc: Michael Meskes <meskes@postgresql.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: deallocating prepared statements
Date: Fri, 12 Dec 2008 12:53:14 +0100
Message-ID: <20081212115314.GA24477@feivel.credativ.de> (raw)
In-Reply-To: <9D29FD18CBD74A478CBA86E6EF6DBAD40308029E@CHI4EVS04.corp.transunion.com>
References: <9D29FD18CBD74A478CBA86E6EF6DBAD402FF8CC9@CHI4EVS04.corp.transunion.com>
<20081203141255.GA1874@feivel.credativ.de>
<9D29FD18CBD74A478CBA86E6EF6DBAD40308029E@CHI4EVS04.corp.transunion.com>
[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!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: meskes@postgresql.org, EHASZLA@transunion.com
Subject: Re: deallocating prepared statements
In-Reply-To: <20081212115314.GA24477@feivel.credativ.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox