From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Deadlock problem |
Date: | 2005-11-18 21:22:48 |
Message-ID: | 20051118212248.GG29354@phlogiston.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, Nov 18, 2005 at 02:49:53PM -0500, Kris Jurka wrote:
> simultaneously, but internally only one is executed at a time. Clearly
> running with autocommit = false requires some coordination of
> transactions, but multiple threads are not in and of themselves dangerous.
I'd _really_ like to see an example of an application that did this
correctly and without any bugs. I've seen people do it, yes; but I
haven't seen it working without fairly serious problems. (Besides,
isn't solving this sort of pain what a pool is for? Why reinvent the
wheel, and make it square to boot?)
A
--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
When my information changes, I alter my conclusions. What do you do sir?
--attr. John Maynard Keynes
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2005-11-18 22:36:25 | ResultSet.getObject returning PGobject |
Previous Message | Kris Jurka | 2005-11-18 19:49:53 | Re: Deadlock problem |