Re: windows doesn't notice backend death

From: justin <justin(at)emproshunts(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: windows doesn't notice backend death
Date: 2009-05-03 20:30:30
Message-ID: 49FDFEE6.1020207@emproshunts.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
>
>
> justin wrote:
>>
>> Would it not be easy to set the normal exitcode to something other
>> than 1 to see the difference
>> ExitProcess()
>>
>
> Not really, as Tom showed later this is an example of a more general
> problem. I think his solution of detecting when backends have cleaned
> up nicely and when they have not is the right way to go.
>
> cheers
>
> andrew
>
Stupid thought why can the some clueless code set the exit status to
crashed status??? Would it not be more prudent to remove that ability???

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-05-03 20:36:50 Re: Why isn't stats_temp_directory automatically created?
Previous Message Robert Haas 2009-05-03 20:13:56 Re: ALTER TABLE ... ALTER COLUMN ... SET DISTINCT