> Part of the problem is that PREPARE has no provision to overwrite an
> existing plan (CREATE OR REPLACE). I run into this all the time because
> I make heavy use of prepared statements to emulate an ISAM file system.
> I have to jump through hoops to keep track of what statements are
> already prepared to keep from bouncing the current transaction.
Bruce - TODO?:
* 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...
In response to
pgsql-hackers by date
|Next:||From: Christopher Kings-Lynne||Date: 2004-06-24 01:45:43|
|Subject: pg_largeobject and tablespaces|
|Previous:||From: Alvaro Herrera||Date: 2004-06-24 01:05:26|
|Subject: Re: nested xacts and phantom Xids|