In attempting to get a new Mingw buildfarm member working, I discovered that there's a rather dramatic and nasty failure when it's built with the latest mingw toolset. If the client passes connection options to the server the server fails miserably with
FATAL: parameter "port" cannot be changed without restarting the server
It doesn't matter what the options setting is. Anything valid at all triggers it.
I've followed several false trails in trying to find what's causing this, and generally wasted a huge amount of time on it. So far I do know that it's apparently not a client problem (and thus not related to putenv, as several of us thought it might be), not related to compiler optimization, not related to compiler version, and not related to the system's getopt version.
For now I'm going to have to give up and do some actual paying work. I'll try to return to it later. Given other demands, that could be some weeks away.
Oh its not just me. Thought I was imagining things.<br />
Anyrate it seems to be something introduced in PostgreSQL 9.0. compiling 8.4 I don't have this problem. Both 9.0 and 9.1 exhibit this problem.<br />
For my purposes I usually test against the VC++ build so haven't been too bothered about it and just build PostgreSQL in mingw to get around PostGIS dependencies on pgxs etc and then do my checks against a VC++ build.