Re: Tab completion of SET TRANSACTION ISOLATION
- From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
- To: Michael Paesold <mpaesold(at)gmx(dot)at>
- Cc: Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Tab completion of SET TRANSACTION ISOLATION
- Date: Tue, 31 Jan 2006 17:16:13 -0300
- Message-id: <20060131201613(dot)GA7181(at)surnet(dot)cl>
Michael Paesold wrote:
> Perhaps not multiple connections, but multiple transactions per connection,
> like Oracle supports, AFAIK. All with a big ;-) of course. I doubt it would
> be easy to implement that. The assumption
> one-connection-has-one-transaction is probably pretty deeply burried in
> many backend components. Has this been changed by the prepared-transactions
> stuff? I may be mistaken, which would be very positive news.
No, you're not mistaken. The 2PC stuff works by reassigning the
transaction to a sort-of "phantom backend".
--
Alvaro Herrera http://www.advogato.org/person/alvherre
"Llegará una época en la que una investigación diligente y prolongada sacará
a la luz cosas que hoy están ocultas" (Séneca, siglo I)
Home |
Main Index |
Thread Index