| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mingw check hung |
| Date: | 2009-01-29 03:36:06 |
| Message-ID: | 49812426.4070506@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>
>>> Andrew Dunstan wrote:
>>>
>>>> The suspect patch is quite definitely the source of the problem.
>>>>
>>
>>
>>> I can't spot the error right off :-( Can you try to see if it's the
>>> putenv() or the unsetenv() that gets broken?
>>>
>>
>> Are we sure pgwin32_unsetenv works in this environment? (Or worse,
>> maybe it's trying to use port/unsetenv.c?)
>>
>>
>>
>
> It is the pgwin32_unsetenv() call that is causing the trouble somehow.
> That much I have just managed to isolate.
>
>
Specifically, it's the SetEnvironmentVariable() call from
pgwin32_putenv() called from pgwin32_unsetenv(). When this is disabled
things work just fine.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-01-29 03:43:41 | Re: How to get SE-PostgreSQL acceptable |
| Previous Message | Robert Haas | 2009-01-29 03:35:22 | Re: How to get SE-PostgreSQL acceptable |