Tue Aug 24 11:59:20 PDT 2010
- Previous message: [Slony1-bugs] [Bug 40] libpq thread test insufficient
- Next message: [Slony1-bugs] [Bug 40] libpq thread test insufficient
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=40 --- Comment #5 from Peter Eisentraut <peter_e at gmx.net> 2010-08-24 11:59:20 PDT --- There is possibly some confusion here. --enable-thread-safety always creates a functionally different libpq on any platform. And a libpq compiled without that flag is not suitable for multithreaded applications on any platform. At least a glance at the source code indicates as much. It might be that you don't actually need the parts in question, but I'm not sure. What you might be thinking of is that on some platforms (including Linux, excluding BSD, I think), most/all libc functions are reentrant by default, without the need for special compiler flags. But that just means that the --enable-thread-safety flag has to do less work, it doesn't make the entire library thread-safe automatically. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
- Previous message: [Slony1-bugs] [Bug 40] libpq thread test insufficient
- Next message: [Slony1-bugs] [Bug 40] libpq thread test insufficient
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list