Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)

On 30 June 2016 at 07:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Tom Lane wrote:
> >> Thanks for investigating! I'll go commit that change. I wish someone
> >> would put up a buildfarm critter using VS2013, though.
>
> > Uh, isn't that what woodlouse is using?
>
> Well, it wasn't reporting this crash, so there's *something* different.
>
>
It may only affect the i386 to x86_64 cross compiler. If Woodlouse is using
native x86_64 compilers perhaps that's why?

We've confirmed it on two different versions of VS 2013, so it's not
specific to one minor compiler point release.

It'd be handy if the buildfarm captured the output of:

* cl (no arguments, first line only)
* msbuild /nologo /version

and the env vars:

* VS*COMNTOOLS (* being any 3 digits)
* PROCESSOR_ARCHITECTURE
* PROCESSOR_IDENTIFIER
* PROCESSOR_ARCHITEW6432

since right now it's hard to be totally sure exactly what a VS animal is
building with unless there's a log attached due to a failure.

That said, TBH I doubt we can or should cover every VS release in every VS
configuration. Especially since there are so many ways you can excitingly
break and mangle VS, particularly when installing multiple VS versions on
one host. It's a great IDE with a truly awful set of installation and
managment tools.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services