Re: windows doesn't notice backend death

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 17:58:55
Message-ID: 49FDDB5F.3030909@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>
>> FWIW, this certainly used to work. So we've either broken this recently,
>> or it's always been broken on Vista (I've never tried it myself on
>> Vista, only 2000, XP and 2003).
>>
>
> Maybe a quick check if it still works on non-Vista versions would be
> in order, to eliminate one or the other of those theories.
>
>
>

Well, I can tell you that it is getting an exit code of 1, which is why
the postmaster isn't restarting.

That raises two questions in my mind. First, is that the behaviour we
expect when we kill the backend this way? And second, why is it still
showing up in the output of pg_stat_activity?

Meanwhile, I guess I can try to create a loadable function that will
crash a backend badly so I can try to reproduce my client's problem.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-05-03 18:14:02 Re: windows doesn't notice backend death
Previous Message Tom Lane 2009-05-03 17:46:19 Re: windows doesn't notice backend death