Re: enable-thread-safety defaults? - Mailing list pgsql-hackers

From Greg Stark
Subject Re: enable-thread-safety defaults?
Date
Msg-id 407d949e0911192347x308e0310tb6a7a47cc8973ea0@mail.gmail.com
Whole thread Raw
In response to Re: enable-thread-safety defaults?  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Fri, Nov 20, 2009 at 7:39 AM, Magnus Hagander <magnus@hagander.net> wrote:
> 2009/11/20 Peter Eisentraut <peter_e@gmx.net>:
>> On fre, 2009-11-20 at 02:41 +0100, Magnus Hagander wrote:
>>> Is there any actual reason why we are building without thread safety
>>> by default on most platforms?
>>
>> Consistent defaults on all platforms?
>
> So why do we have largefile enabled by default? And zlib? And readline?

Well those things are user interface options. They don't change the libpq api.

However given that distributions set this option I don't see much
point in worrying about the api being inconsistent. I agree that
having libpq being thread-safe would be a sensible default.


-- 
greg


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Summary and Plan for Hot Standby
Next
From: Kris Jurka
Date:
Subject: Re: [COMMITTERS] pgsql: /home/peter/commit-msg