I still believe this "exit code 128" is related to pgAdmin opened during the clossing session on Remote Desktop. I have
aWindows user login wich is not administrator just no privileged user, it cannot start/stop services, just monitoring.
WithpgAdmin window opened inside my disconected session, as Administrator if I "close" the another disconnected
session,Postgres exit with 128 code. <br /><br />Did you reproduce this behavior?<br /><br />Cristian.<br /><br /><div
class="gmail_quote">2010/8/26Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span><br/><blockquote class="gmail_quote" style="margin: 0pt
0pt0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">Robert Haas <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>writes:<br /></div><div class="im">> On Tue, Aug
24,2010 at 9:58 AM, Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> wrote:<br /></div><div
class="im">>>Given the existence of the deadman switch mechanism (which I hadn't<br /> >> remembered when
thisthread started), I'm coming around to the idea that<br /> >> we could just treat exit(128) as nonfatal on
Windows. If for some<br /> >> reason the child hadn't died instantly at startup, the deadman switch<br />
>>would distinguish that from the case described here.<br /><br /> > So do you want to code this up?<br /><br
/></div>Who,me? I don't do Windows --- I'd have no way to test it.<br /><br /> regards, tom
lane<br/></blockquote></div><br />