Tue Aug 24 12:48:11 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 #6 from Jan Wieck <janwieck at yahoo.com> 2010-08-24 12:48:11 PDT --- Correct, Peter. Slony is multi threaded, but never do two threads use the same database connection or any object derived there of. Maybe that is why it does work on some platforms that don't actually produce a 100% thread safe libpq without --enable-thread-safety. What I would suggest is that we collect a slightly longer list of OS's, where this is irrelevant for Slony and then make this a test with 3 possible outcomes. Error out if --enable-thread-safety wasn't used where we know it needs to be (aix, solaris), Don't care if it was (Linux, FreeBSD) and give a WARNING for everything else. This has IMHO time until 2.0.6 -- 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