Re: PREPARE and transactions - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PREPARE and transactions
Date
Msg-id 200407110309.i6B39r824701@candle.pha.pa.us
Whole thread Raw
In response to Re: PREPARE and transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
What was the conclusion for PREPARE done inside transactions?

---------------------------------------------------------------------------

Tom Lane wrote:
> "Jeroen T. Vermeulen" <jtv@xs4all.nl> writes:
> > I think we're talking at cross purposes here...  If the client doesn't use
> > explicit transactions, as you say is common, then you're obviously not
> > defining prepared statements inside explicit transactions either.
> 
> This whole discussion seems to be considering only the case of PREPAREs
> issued as SQL statements, by a programmer who is fully cognizant of
> where he's beginning and ending transactions.
> 
> The issue I was trying to raise at the beginning of the thread was: what
> about prepared statements created by client libraries (think JDBC for
> instance) using the V3 protocol Parse message?  Rolling back a
> successful prepare because of a later transaction failure seems like
> exactly not what such a library would want.
> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PREPARE and transactions
Next
From: Bruce Momjian
Date:
Subject: Re: pg_largeobject and tablespaces