Re: The real reason why TAP testing isn't ready for prime time - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: The real reason why TAP testing isn't ready for prime time
Date
Msg-id 20150619191925.GQ133018@postgresql.org
Whole thread Raw
In response to Re: The real reason why TAP testing isn't ready for prime time  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2015-06-19 13:56:21 -0300, Alvaro Herrera wrote:
> >> We discussed this when that patch got in (82233ce7ea42d6b).  The reason
> >> for not waiting, it was argued, is that the most likely reason for those
> >> processes not to have already gone away by the time we send SIGKILL was
> >> that they are stuck somewhere in the kernel, and so we might not be able
> >> to actually get them to go away with the SIGKILL.  As I recall, that was
> >> the actual problem that MauMau was trying to get fixed.
> 
> > How does exiting before they're dead help? They're still going to be
> > attached to shared memeory and thus prevent a restart. I don't think
> > hiding the problem by exiting the postmaster helps at all.
> 
> My thought exactly.

I guess you have a point there.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_regress not waiting for postmaster to stop
Next
From: Josh Berkus
Date:
Subject: Re: pgbench - allow backslash-continuations in custom scripts