From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: enable-thread-safety defaults? |
Date: | 2009-11-20 14:25:32 |
Message-ID: | 4B06A6DC.8090705@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut wrote:
>
> 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.
>
>
Well, if we turn it on by default maybe the buildfarm will tell us who
the major culprits are :-)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alexey Klyukin | 2009-11-20 14:34:45 | Re: plperl and inline functions -- first draft |
Previous Message | Tim Bunce | 2009-11-20 13:50:04 | Re: plperl and inline functions -- first draft |