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

On Fri, Jun 24, 2016 at 2:14 AM, Umair Shahid <umair(dot)shahid(at)2ndquadrant(dot)com>
wrote:

>
> ---------- Forwarded message ----------
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date: Thu, Jun 23, 2016 at 9:32 PM
> Subject: Re: [pgsql-packagers] PG 9.6beta2 tarballs are ready
> To: Magnus Hagander <magnus(at)hagander(dot)net>
> Cc: Umair Shahid <umair(dot)shahid(at)2ndquadrant(dot)com>, Dave Page <
> dpage(at)postgresql(dot)org>, PostgreSQL Packagers <
> pgsql-packagers(at)postgresql(dot)org>
>
>
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > That makes more sense as the joinrel stuff *has* been changed between the
> > two betas. I'm sure someone who's touched that code (Tom?) can comment on
> > that part..
>
> It still makes little sense to me, as the previous reports say that the
> problem happened during bootstrap, and the planner does not run
> during bootstrap.
>
> Could we get a look at debug_query_string in the coredump, to possibly
> narrow down where the crash is really happening?
>

Moving thread to -hackers ...

debug_query_string is

* "INSERT INTO pg_description SELECT t.objoid, c.oid, t.objsubid,
t.description FROM tmp_pg_description t, pg_class c WHERE c.relname =
t.classname;"*

Happening in "setup_description"

>
> > It's still strange that it doesn't affect woodlouse.
>
> Or any of the other Windows critters...
>
> regards, tom lane
>
>
>
> --
> Umair Shahid
> 2ndQuadrant - The PostgreSQL Support Company
> http://www.2ndQuadrant.com/
>