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

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)
Дата
Msg-id CAMsr+YHWLrLewDwGhNpWaEbEoyjjc7qzUA0in-EUnUNhzOq8ww@mail.gmail.com
обсуждение исходный текст
Ответ на initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)  (Umair Shahid <umair.shahid@gmail.com>)
Ответы Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)  (Michael Paquier <michael.paquier@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: tuplesort.c's copytup_index() is dead code
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)