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

Re: PREPARE and transactions

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>
Cc: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: PREPARE and transactions
Date: 2004-06-24 01:35:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> 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?:


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-LynneDate: 2004-06-24 01:45:43
Subject: pg_largeobject and tablespaces
Previous:From: Alvaro HerreraDate: 2004-06-24 01:05:26
Subject: Re: nested xacts and phantom Xids

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