Tom Lane wrote: <blockquote cite="mid:28338.1241374442@sss.pgh.pa.us" type="cite"><pre wrap=""> Have M$ really been stupid enough to make an external kill look just like an exit() call? regards, tom lane </pre></blockquote><font face="Arial">kind of :-(<br /><br /> Everything i have read seems to point the Task Manager callsTerminateProcess() in the kernel32.dll and passes a 1 setting the exitcode to 1. I have not found anything clearlystating that, yet logic points that is what its doing. <br /><br /><a class="moz-txt-link-freetext" href="http://msdn.microsoft.com/en-us/library/ms686714(VS.85).aspx">http://msdn.microsoft.com/en-us/library/ms686714(VS.85).aspx</a><br /><br/> Would it not be easy to set the normal exitcode to something other than 1 to see the difference <br /> ExitProcess()<br/><a class="moz-txt-link-freetext" href="http://msdn.microsoft.com/en-us/library/ms682658(VS.85).aspx">http://msdn.microsoft.com/en-us/library/ms682658(VS.85).aspx</a><br /><br/><br /> this article maybe helpful. <br /><a class="moz-txt-link-freetext" href="http://msdn.microsoft.com/en-us/library/ms686722(VS.85).aspx">http://msdn.microsoft.com/en-us/library/ms686722(VS.85).aspx</a><br /><br/> BTW tested on Windows 2003 SP1 this problem shows up in Postgresql 8.3.3<br /></font>
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных
