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

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Umair Shahid <umair(dot)shahid(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)
Date: 2016-06-24 04:28:22
Message-ID: CAMsr+YHWLrLewDwGhNpWaEbEoyjjc7qzUA0in-EUnUNhzOq8ww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24 June 2016 at 05:17, Umair Shahid <umair(dot)shahid(at)gmail(dot)com> wrote:

>
>> > It's still strange that it doesn't affect woodlouse.
>>
>> Or any of the other Windows critters...
>> <http://www.2ndQuadrant.com/>
>>
>
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

In response to

Responses

Browse pgsql-hackers by date

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