Re: initdb crash

>> > Hm.  Whether those macros are wrong or not, we're still
>left wondering
>> > why it would exit(5), either.
>> >
>> > The crash is apparently coming during the first attempt to
>insert a row
>> > from the postgres.bki file.  That does not seem consistent with the
>> > theory about a permissions problem; if we had no directory
>permissions
>> > I'd have expected a failure at the previous "create
>pg_proc" step.  (For
>> > that matter, how'd we have managed to create all the
>subdirectories and
>> > configuration files?  The permissions theory doesn't hold
>water at all.)
>> >
>> >             regards, tom lane
>>
>
>Hmm, I've just rebuilt this from the latest source snapshot
>tarball and it works perfectly.
>Could this be a bad build of the binary on the snapshot website?

It could be. It's starting to sound more and more like it. I've tried a
whole bunch of different permission sets on dirs/parents/etc, and I'm
completley unable to reproduce the problem.

Looking at the build switches, the difference is I'm building without
zlib and without ssl, but with asserts enabled. Unfort, my mingw env is
a bit broken, so I can't try it with zlib and ssl enabled. Could you try
that (the exact commandline is on the www.hagander.net/pgsql/win32snap/
page), and see if one of those switches is what causes the problem?

Merlin - can you comment on wether that commandline used to build is
correct or if it has changed lately, and wether you see the same
problem?


//Magnus