From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Mixing threaded and non-threaded |
Date: | 2004-01-14 06:40:09 |
Message-ID: | 20040114064009.GA3324@gp.word-to-the-wise.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Cave-Ayland | 2004-01-14 09:54:50 | Re: Suggestions for analyze patch required... |
Previous Message | Tom Lane | 2004-01-14 04:53:12 | VACUUM delay (was Re: What's planned for 7.5?) |