Re: Named transaction
От | Joshua D. Drake |
---|---|
Тема | Re: Named transaction |
Дата | |
Msg-id | 1245267789.14354.59.camel@jd-laptop.pragmaticzealot.org обсуждение исходный текст |
Ответ на | Re: Named transaction ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Список | pgsql-hackers |
On Wed, 2009-06-17 at 14:38 -0500, Kevin Grittner wrote: > Tom Lane <tgl@sss.pgh.pa.us> wrote: > > > Yes, but some other followups suggest that maybe a "named > > transaction" does something else entirely. Thus my request for a > > definition of what the OP is actually asking for. > > Well, a quick google search suggests that all three guesses here were > off base. This is the best clue I could find with a two-minute > perusal: > > # TRANSACTION_HANDLE -> use a named transaction. Firebird allows > # multiple transactions per connection. In the case below, this > # request is run in the system transaction - not available outside the > # engine. The system transaction number is 0 and it is > # "pre-committed" meaning that its changes are immediately visible to > # all other transactions. > > Does that send a nasty chill up anyone else's spine? That sounds like dirty read, IIRC. Joshua D. Drake -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
В списке pgsql-hackers по дате отправления: