Re: [Re] Re: PREPARE and transactions
От | Greg Sabino Mullane |
---|---|
Тема | Re: [Re] Re: PREPARE and transactions |
Дата | |
Msg-id | 68bcd79ed96a3c6b53ea4c1eac856f17@biglumber.com обсуждение исходный текст |
Ответ на | Re: [Re] Re: PREPARE and transactions (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: [Re] Re: PREPARE and transactions
|
Список | pgsql-hackers |
-----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@turnstep.com PGP Key: 0x14964AC8 200407062132 -----BEGIN PGP SIGNATURE----- iD8DBQFA61K/vJuQZxSWSsgRAi6oAKDruPbDxfk2uDydOAPoFLjJxyeaHACfaT3V LncDJ2/eFy8RMNLbmcG2Iwo= =Tin2 -----END PGP SIGNATURE-----
В списке pgsql-hackers по дате отправления: