(I hope this is -hackers appropriate - feel free to point me elsewhere) I'm using 7.4.1 as the backend to several applications. Until recently, I've been developing solely single-threaded applications.
I just rebuilt postgresql with --enable-thread-safety, to work with some multi-threaded code. When I rebuilt libpq to use threads, I started seeing a bunch of weird failures in many of the older applications. The change in libpq meant that libpthread was being dynamically linked into the non-thread-aware applications, leading to some mutex deadlocks in their signal handlers, hanging those applications. There doesn't seem to be any tidy way to build and use both threaded and non-threaded libpq on the same system (LD_LIBRARY_PATH hacks aren't really viable for distributed code). Is there something I'm missing? (If it's relevant, the OS in question is RedHat Linux, but I'm maintaining the same suite of apps on several other architectures.) Cheers, Steve ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
