Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session - Mailing list pgsql-hackers

From Cristian Bittel
Subject Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session
Date
Msg-id AANLkTikOPEGrF6dAZkYx1=vjmu2oUdyikg=ydXOnr0Sx@mail.gmail.com
Whole thread
In response to Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session
List pgsql-hackers
I still believe this "exit code 128" is related to pgAdmin opened during the clossing session on Remote Desktop. I have a Windows user login wich is not administrator just no privileged user, it cannot start/stop services, just monitoring. With pgAdmin window opened inside my disconected session, as Administrator if I "close" the another disconnected session, Postgres exit with 128 code.

Did you reproduce this behavior?

Cristian.

2010/8/26 Tom Lane <tgl@sss.pgh.pa.us>
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Aug 24, 2010 at 9:58 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Given the existence of the deadman switch mechanism (which I hadn't
>> remembered when this thread started), I'm coming around to the idea that
>> we could just treat exit(128) as nonfatal on Windows.  If for some
>> reason the child hadn't died instantly at startup, the deadman switch
>> would distinguish that from the case described here.

> So do you want to code this up?

Who, me?  I don't do Windows --- I'd have no way to test it.

                       regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: About the types of fields in a data structure
Next
From: Robert Haas
Date:
Subject: Re: bg worker: patch 1 of 6 - permanent process