Re: Thread configure flag

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Thread configure flag
Date: 2003-06-17 18:14:59
Message-ID: 14227.1055873699@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> I have heard that the reentrant libc is significantly worse-performing
>> than the non-reentrant one on some platforms. This is not real hard
>> to believe, since functions as common as malloc() will need locking
>> overhead if they think they might be in a multithreaded environment.

> Then maybe we should make a libpq and a libpq_r, etc.

That would be fine with me ... although it's only worth doing if the
platform has a libc and a libc_r. Shall we use the existence of libc_r
to drive this choice?

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruno Wolff III 2003-06-17 20:32:32 ss_family in hba.c
Previous Message Larry Rosenman 2003-06-17 18:03:58 Re: Thread configure flag