Re: [bug fix] "pg_ctl stop" times out when it should respond quickly - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [bug fix] "pg_ctl stop" times out when it should respond quickly
Date
Msg-id CA+TgmobP2n62fBjmRdt=-iYXMnhF9GwpUe2p3OkjB0oYbn=gHw@mail.gmail.com
Whole thread Raw
In response to Re: [bug fix] "pg_ctl stop" times out when it should respond quickly  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [bug fix] "pg_ctl stop" times out when it should respond quickly  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Feb 17, 2014 at 11:29 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> The pg_regress part is ugly.  However, pg_regress is doing something
> unusual when starting postmaster itself, so the ugly coding to stop it
> seems to match.  If we wanted to avoid the ugliness here, the right fix
> would be to use pg_ctl to start postmaster as well as to stop it.

I wonder if this would change the behavior in cases where we hit ^C
during the regression tests.  Right now I think that kills the
postmaster as well as pg_regress, but if we used pg_ctl, it might not,
because pg_regress uses fork()+exec(), but pg_ctl uses system() to
launch a shell which is in turn instructed to background the
postmaster.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Description for pg_replslot in docs
Next
From: Robert Haas
Date:
Subject: Re: should we add a XLogRecPtr/LSN SQL type?