Re: Complier warnings on mingw gcc 4.5.0 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Complier warnings on mingw gcc 4.5.0
Date
Msg-id 5852.1292426221@sss.pgh.pa.us
Whole thread Raw
In response to Re: Complier warnings on mingw gcc 4.5.0  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Complier warnings on mingw gcc 4.5.0  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Andrew Dunstan's message of mié dic 15 02:08:24 -0300 2010:
>> That didn't work. But git bisect says it's this commit that's to blame:
>> <https://github.com/postgres/postgres/commit/e710b65c1c56ca7b91f662c63d37ff2e72862a94>

> Hmm I wonder if this is reproducible in a non-Windows EXEC_BACKEND
> scenario.

I'm pretty sure I tried the no-flat-files code in that scenario while
writing it.  But it might be worth trying that again.  You'd think
though that if EXEC_BACKEND were sufficient to provoke it, all Windows
builds would fail.  I'm still mystified by what is the difference
between Andrew's non-working installation and working mingw builds.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: hstores in pl/python
Next
From: Dmitriy Igrishin
Date:
Subject: Re: hstores in pl/python