From: | Larry Rosenman <ler(at)lerctr(dot)org> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use |
Date: | 2004-03-22 17:14:59 |
Message-ID: | 61350000.1079975699@lerlaptop.lerctr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
--On Monday, March 22, 2004 09:52:54 -0500 Bruce Momjian
<pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Bruce Momjian wrote:
>> Larry Rosenman wrote:
>> > The a.out (not any library) should be linked with -Kpthread (not
>> > -lpthread).
>> > This will force libthread to be linked in the right order relative to
>> > libc, libC, networking libraries, etc.
>> >
>> > In other words, the entire application either is or is not linked with
>> > threads; it's not a property of an individual library.
>> >
>> >
>> > SO, IF we are using the threads flags, we need to use them on ALL
>> > libpq-using programs, ours or the users.
>>
>> Seems we have a few options for making threaded libpq on Unixware:
>>
>> o remove thread-safe SIGPIPE code, which calls thread library
>>
>> o create a threaded and non-threaded libpq library
>>
>> o add a libpq function that enables threading, and do dynamic
>> linking of thread calls based on that function
>>
>> o Add thread flags to all builds on that platform, including
>> the backend
>>
>> o Add the ability to specify compile/link flags for everything
>> but the backend
>>
>> As I remember, libcrypt used to be required by all libpq builds on
>> various platforms. This seems to be a similar case.
>>
>> I think the last option might be the best. Somehow create different
>> cppflags/libs for the backend and non-backend programs.
>
> One other option is to disable threads on this platform for 7.5 unless
> we find another platforms that need this to use threads. That is the
> direction I will take for the moment. If someone needs a threaded libpq
> on this platform, then can enable threads, compile libpq alone, and
> rename it with a thread extension.
This will be a REGRESSION from 7.4. I object STRENUOUSLY to this tack.
I want to see threads enabled for this platform since it is a threaded
kernel.
What do we have to do to get there? What code do I need to write for
y'all?
LER
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
> 19073
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-22 17:33:56 | Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use |
Previous Message | Fabien COELHO | 2004-03-22 16:35:29 | Re: Syntax error reporting (was Re: [PATCHES] syntax error |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-22 17:33:56 | Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use |
Previous Message | Fabien COELHO | 2004-03-22 16:35:29 | Re: Syntax error reporting (was Re: [PATCHES] syntax error |