| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Named transaction |
| Date: | 2009-06-17 19:43:09 |
| Message-ID: | 1245267789.14354.59.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-06-17 at 14:38 -0500, Kevin Grittner wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-06-17 19:51:02 | Re: Named transaction |
| Previous Message | Kevin Grittner | 2009-06-17 19:38:19 | Re: Named transaction |