Re: threads stuff/UnixWare - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: threads stuff/UnixWare
Date
Msg-id 200405130226.i4D2Q3L29350@candle.pha.pa.us
Whole thread Raw
In response to Re: threads stuff/UnixWare  (Larry Rosenman <ler@lerctr.org>)
Responses Re: threads stuff/UnixWare  (Larry Rosenman <ler@lerctr.org>)
List pgsql-hackers
Larry Rosenman wrote:
> Yes, there would still be the overhead, because the functions that 
> libthread wraps would go through that overhead since libthread does it's 
> magic at _ini time.
> 
> Y'all were concerned with overhead in previous discussions.
> 
> If you want to link the backend with -Kpthread, you can, but basically the
> client code (initdb, et al) should be -Kpthread, and the backend should NOT
> since there are no threads calls in the backend.
> 
> >
> > I am afraid of libpgport.  Those object files get used by the backend,
> > and by the client stuff.  Larry can -K and non-K object files be mixed
> > in the same binary?
> Yes, they can.
> 
> But, you MUST link ANY pthread_* using code with -K pthread.

OK, can someone come up with a cute way to add flags only to things that
use libpq, meaning /interfaces and /bin?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Subtle pg_dump problem...
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Subtle pg_dump problem...