Re: More legacy code: pg_ctl - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: More legacy code: pg_ctl
Date
Msg-id 52A0902D.6020501@gmx.net
Whole thread Raw
In response to More legacy code: pg_ctl  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 11/18/13, 8:09 PM, Josh Berkus wrote:
> a) by default, it returns to the caller without waiting for postgres to
> actually start/stop/restart.  In this mode, it also always returns
> success regardless of result.

The reason for this is that until sometime recently (PQping) we didn't
have a reliable way to check whether the server is up.  This might be
different now, but it would need to be verified.

> b) by default, it remains attached to the caller's tty for stdout and
> stderr, even after it has switched to the regular postgres log.

Can pg_ctl tell when the postgres log has switched?



pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Backup throttling
Next
From: Peter Eisentraut
Date:
Subject: Re: More legacy code: pg_ctl