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

Re: PREPARE and transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
Cc: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>,pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Subject: Re: PREPARE and transactions
Date: 2004-06-25 14:02:29
Message-ID: 6350.1088172149@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> 1. Add a "soft" bit to prepared-statement plans
> 2. Add rollback bookkeeping for prepared statements, which sets the bit
> 3. Accept identical re-preparations of "soft" statements, clearing the bit

That sounds awfully ugly :-(

It occurs to me that a lot of the problem would go away if we allowed
DEALLOCATE of a nonexistent statement to not be an error (seems like
a NOTICE would be be plenty).  Then you could just unconditionally
DEALLOCATE anything you were about to PREPARE, if you weren't entirely
sure whether it already existed.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Jeroen T. VermeulenDate: 2004-06-25 14:20:53
Subject: Re: PREPARE and transactions
Previous:From: Jeroen T. VermeulenDate: 2004-06-25 13:25:58
Subject: Re: PREPARE and transactions

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