Re: Complier warnings on mingw gcc 4.5.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: 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-13 17:01:10
Message-ID: 9485.1292259670@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 11/01/2010 10:10 PM, Itagaki Takahiro wrote:
>> BTW, with out without the above fix, regression test failed with
>> weird error if the server is built with gcc 4.5. However, server
>> can run if I started it manually with PGPORT or -o "--port=X".
>> We might need another fix for the issue.
>> ----
>> LOG: database system was shut down at 2010-11-02 10:32:13 JST
>> LOG: database system is ready to accept connections
>> LOG: autovacuum launcher started
>> FATAL: parameter "port" cannot be changed without restarting the server
>> (repeated)

> I have just run into this when trying to set up a new buildfarm member
> running Mingw. Is there a fix? Is anyone working on it? Or do I just
> need to downgrade the compiler?

It smells a little bit like an optimization bug. Does dialing down to
-O0 make it go away?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-12-13 17:04:23 Re: hstores in pl/python
Previous Message Andrew Dunstan 2010-12-13 16:37:57 Re: [COMMITTERS] pgsql: Use symbolic names not octal constants for file permission flags