On Thu, 7 Feb 2002 mkscott@sacadia.com wrote:
> Making postgres functions thread-safe increases the flexibility of the
> codebase. Whether threading connections, sub-queries, increasing
> processor utilization, or some other unforseen optimization, having
> reentrant and thread-safe code leaves the door open for new ideas. Yes,
> writing reenterant code can be restrictive and a little more complex,
> but not much, the big work is the upfront cost of porting. I have done
> it done it once and gained a great deal on projects that I am working
> on.
Would be willing to take what you've learnt and work with the current CVS
tree towards making her thread-safe? Even small steps regularly taken
brings us closer to being able to use even *some* threading in the backend
...
