« Return to Thread: [Patch] - Fix for bug #2558, InitDB failed to run on windows 2003

Re: [Patch] - Fix for bug #2558, InitDB failed to run

by Bugzilla from pgadmin@pse-consulting.de :: Rate this Message:

Reply to Author | View in Thread

Bruce Momjian wrote:

> Andreas Pflug wrote:
>> Tom Lane wrote:
>>> Andrew Dunstan <andrew@...> writes:
>>>  
>>>> I am more than somewhat perplexed as to why the NUL device should be a
>>>> security risk ... what are they thinking??
>>>>    
>>> Frankly, I don't believe it; even Microsoft can't be that stupid.
>>> And I can't find any suggestion that they've done this in a google
>>> search.  I think the OP is misdiagnosing his problem.
>>>  
>> An older message suggests that a service pack induced this problem, per
>> MS. I just tried it as non-admin on a W2K3 machine with recent hotfixes,
>> and the command "dir >nul" _did_ work for me.
>> Though neglected, it still sounds like a virus scanner issue to me.
>
> Yes, it seems we will need more information on this.  We need someone at
> a win32 command prompt to show us a "> nul" failure.

OTOH,
what issues might arise if the output is redirected to a legal tmp file?

Regards,
Andreas

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

 « Return to Thread: [Patch] - Fix for bug #2558, InitDB failed to run on windows 2003