From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: enable-thread-safety defaults? |
Date: | 2009-11-20 08:30:07 |
Message-ID: | 1258705807.28720.8.camel@fsopti579.F-Secure.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On fre, 2009-11-20 at 08:39 +0100, Magnus Hagander 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?
Let me be more verbose: I would assume that we want the configure
defaults to be the same on all platforms. We fail by default, for
example, if zlib and readline are not there, but you can turn them off
explicitly. If we turn thread-safety on by default, we will/should fail
if thread-safety is not supported, requiring the user to turn it off
explicitly. If enough platforms don't support thread-safety, this could
become annoying.
I don't have a good overview over how many platforms would be affected,
and I could in general support changing the default, but I'm just laying
down one possible constraint.
From | Date | Subject | |
---|---|---|---|
Next Message | Joachim Wieland | 2009-11-20 08:34:16 | Re: Listen / Notify - what to do when the queue is full |
Previous Message | Peter Eisentraut | 2009-11-20 08:26:45 | Re: Python 3.1 support |