Magnus Hagander wrote:
>>This took me hours to find ...
>>On my Windows box, CVS HEAD gets an execution failure on "initdb foo"
>>but succeeds happily with "initdb -D foo".
>>This is not true for REL8_1_STABLE, nor is it true for all
>>Windows machines/environments, apparently, otherwise we would
>>be seeing failures from the buildfarm member snake, since the
>>buildfarm script does "initdb data".
>>My suspicion is that this is some side effect of the
>>restricted-exec patch, but I don't have time to dig further right now.
>Um, so what error msg do you get when it's failing?
I get a popup box that says:
initdb.exe has encountered a problem and needs to close.
We are sorry for the inconvenience.
Clicking a link gives this info:
AppName: initdb.exe AppVer: 18.104.22.16851 ModName: msvcrt.dll
ModVer: 7.0.2600.1106 Offset: 00033830
It wouldn't let me copy the rest of the info ;-(
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2006-02-21 18:35:00|
|Subject: Re: windows / initdb oddness|
|Previous:||From: Stephan Szabo||Date: 2006-02-21 16:48:25|
|Subject: Re: pg_config, pg_service.conf, postgresql.conf ....|