Skip site navigation (1) Skip section navigation (2)

Re: PREPARE and transactions

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PREPARE and transactions
Date: 2004-06-24 03:29:09
Message-ID: 73b63b6c5b26a388560ffed597f13474@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
 
Merlin Moncure wrote:
> I have to jump through hoops to keep track of what statements are
> already prepared to keep from bouncing the current transaction.
 
Christopher Kings-Lynne wrote:
> * PREPARE OR REPLACE...
>
> This would be an incredibly useful command since there's no
> way of _checking_ in advance that a name is already used as a
> prepared statement...
 
A check would be nice (and I've asked about it before) but it's
really not a lot of jumping through hoops since each connection has
it's own "namespace" of prepared statements. Since they last until
an explicit deallocate, the simple use of unique names makes it
fairly easy on the application side.
 
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200406232330
 
-----BEGIN PGP SIGNATURE-----
 
iD8DBQFA2krxvJuQZxSWSsgRAhLSAJ9othitQerDlB9+J65rVl3EbRT9+QCeJfzH
vFdWCDLvxU/zkFMLEDjpydU=
=OzCx
-----END PGP SIGNATURE-----



In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-06-24 03:53:42
Subject: Re: pg_largeobject and tablespaces
Previous:From: Tom LaneDate: 2004-06-24 03:28:27
Subject: Re: nested xacts and phantom Xids

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group