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) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
