| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Complier warnings on mingw gcc 4.5.0 |
| Date: | 2010-12-15 15:17:01 |
| Message-ID: | 5852.1292426221@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2010-12-15 15:18:06 | Re: hstores in pl/python |
| Previous Message | Dimitri Fontaine | 2010-12-15 15:15:09 | Re: hstores in pl/python |