| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: enable-thread-safety defaults? |
| Date: | 2009-11-20 07:47:50 |
| Message-ID: | 407d949e0911192347x308e0310tb6a7a47cc8973ea0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 20, 2009 at 7:39 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> 2009/11/20 Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2009-11-20 08:11:55 | Re: [HACKERS] pgsql: /home/peter/commit-msg |
| Previous Message | Josh Berkus | 2009-11-20 07:40:53 | Re: Summary and Plan for Hot Standby |