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

From Craig Ringer
Subject Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)
Date
Msg-id CAMsr+YHWLrLewDwGhNpWaEbEoyjjc7qzUA0in-EUnUNhzOq8ww@mail.gmail.com
Whole thread Raw
In response to initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)  (Umair Shahid <umair.shahid@gmail.com>)
Responses Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers


On 24 June 2016 at 05:17, Umair Shahid <umair.shahid@gmail.com> wrote:
 

> It's still strange that it doesn't affect woodlouse.

Or any of the other Windows critters...

Given that it's only been seen in VS 2013, it's particularly odd that it's not biting woodlouse. 

I'd like more details from those whose installs are crashing. What exact vcvars env did you run under, with which exact cl.exe version?



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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: tuplesort.c's copytup_index() is dead code
Next
From: Michael Paquier
Date:
Subject: Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)