-----BEGIN PGP SIGNED MESSAGE-----
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-----
-----END PGP SIGNATURE-----
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2004-06-24 03:53:42|
|Subject: Re: pg_largeobject and tablespaces |
|Previous:||From: Tom Lane||Date: 2004-06-24 03:28:27|
|Subject: Re: nested xacts and phantom Xids |