Re: [Re] Re: PREPARE and transactions

Were are we on deciding how PREPARE in aborted transactions should behave?

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

Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > Other exceptions I can think of are FETCH and DEALLOCATE. DEALLOCATE is
> > particularly fun -- don't most of the arguments for making PREPARE
> > transactional also apply to DEALLOCATE? Is it actually feasible to roll
> > back a DEALLOCATE?
>
> That's why PREPARE and DEALLOCATE are so perfect the way they are: outside
> of transactions. Although I think Tom mentioned that deallocating a
> statement that did not exist should raise a notice and not change the
> transaction status, which I would totally agree with.
>
> - --
> Greg Sabino Mullane greg(at)turnstep(dot)com
> PGP Key: 0x14964AC8 200407062132
> -----BEGIN PGP SIGNATURE-----
>
> iD8DBQFA61K/vJuQZxSWSsgRAi6oAKDruPbDxfk2uDydOAPoFLjJxyeaHACfaT3V
> LncDJ2/eFy8RMNLbmcG2Iwo=
> =Tin2
> -----END PGP SIGNATURE-----
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
[ Decrypting message... End of raw data. ]

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