| From: | Robert Creager <robert(at)logicalchaos(dot)org> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_crypto failures with llvm on OSX |
| Date: | 2012-03-11 03:01:33 |
| Message-ID: | 6C995C10-390B-4B54-86F1-26F039256EB2@logicalchaos.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 10, 2012, at 7:54 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> On 03/10/2012 09:15 PM, Tom Lane wrote:
>>
>> (I wonder whether it'd be a good idea for the buildfarm script to
>> explicitly clear anything that autoconf pays attention to from its
>> startup environment, so that you have to set these variables in the
>> buildfarm config to make them have effect. If not that, maybe print
>> "env" output to document what the situation is?)
>>
>>
>
> I can put the latter in the next client release, unless people think it's a bit insecure to report arbitrary environment values. If we were to clear them, which would we clear?
Why it just report the pertinent ones?
Rob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-03-11 03:41:11 | Re: pg_prewarm |
| Previous Message | Andrew Dunstan | 2012-03-11 02:54:29 | Re: pg_crypto failures with llvm on OSX |