Search Postgresql Archives

Re: Child program using parent program's transaction?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 06, 2006 at 03:21:04PM -0700, Wayne Conrad wrote:
> Today, it would once again be convenient to have an exec'd program do
> its work in the context of its parent program's transaction.  So,
> before I once again decide that I don't actually want to do that, can
> you tell me... is it possible?  And, would any sane person do it?

This isn't exactly the same thing, but I've seen something similar
done with threads.  What I have to say about it is that it appears to
be easy to do when you decide to do it, but it turns out to be hard
to do well in practice.  I cannot count the number of bugs I've come
across because of poor handling of this sort of situation.  In
particular, in my experience, what you start to realise is that the
handoff period is super ultra critical, and subject to all sorts of
nasty race conditions; so you start locking things up in an effort to
avoid the race.  In no time at all, the whole application has ground
to a halt while everything goes through this serialised global
choke-point.  It is at this point that you decide there's a reason
the system doesn't do this sort of thing out of the box ;-)

A

-- 
Andrew Sullivan  | ajs@xxxxxxxxxxxxxxx
Everything that happens in the world happens at some place.
		--Jane Jacobs 


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux