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

From Tom Lane
Subject Re: The real reason why TAP testing isn't ready for prime time
Date
Msg-id 18664.1434728693@sss.pgh.pa.us
Whole thread Raw
In response to Re: The real reason why TAP testing isn't ready for prime time  (Andres Freund <andres@anarazel.de>)
Responses Re: The real reason why TAP testing isn't ready for prime time  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: The real reason why TAP testing isn't ready for prime time  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2015-06-19 11:16:18 -0400, Robert Haas wrote:
>> On Fri, Jun 19, 2015 at 11:07 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> I wonder whether it's such a good idea for the postmaster to give
>>> up waiting before all children are gone (postmaster.c:1722 in HEAD).

>> I doubt it.

> Seconded. It's pretty bad to possibly not be able to start again after
> stopping it. I don't see the benefit in not waiting - sure, the
> poastmaster exits faster, but postgres hasn't shut down at that point...

Yeah.  I'll see about fixing this.  Hard to be sure if it will fix
hamster's issue though.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Inheritance planner CPU and memory usage change since 9.3.2
Next
From: Robert Haas
Date:
Subject: outstanding multixact bugs