http://www.slony.info/bugzilla/show_bug.cgi?id=40

--- Comment #7 from Steve Singer <ssinger at ca.afilias.info> 2010-08-24 13:01:04 PDT ---
While slony does not have multiple threads using the same libpq connection it
does have multiple threads accessing libpq on different connections at the same
time.

Does this mean that we do need to be running with --enable-thread-saftey ?

I haven't looked very closely at the parts of libpq that change based on
ENABLE_THREAD_SAFETY and it looks like we do provide callbacks to openssl for
locking.   I suspect slony needs this on ALL platforms to be safe.

There have been reports I've seen of slony replication breaking over ssl
connections maybe this could have been related.

I think we should modify the patch to require slony to be built with a
threadsafe libpq on all platforms.

-- 
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.