Re: Thread configure flag

Peter Eisentraut <peter_e@gmx.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