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+YHW4xnUnbQpsoowVxvyVnENfRQEgjfsbiqg+Fxgo5wv2A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready) (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: initdb issue on 64-bit Windows - (Was:
[pgsql-packagers] PG 9.6beta2 tarballs are ready)
|
Список | pgsql-hackers |
On 30 June 2016 at 20:19, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Craig Ringer wrote:
> On 30 June 2016 at 07:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> > Alvaro Herrera <alvherre@2ndquadrant.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?
Hmm, so what about a pure 32bit build, if such a thing still exists? If
so and it causes the same crash, perhaps we should have one member for
each VS version running on 32bit x86.
It's fine for a pure 32-bit build, i.e. 32-bit tools and 32-bit target. I tested that.
В списке pgsql-hackers по дате отправления: