| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: More legacy code: pg_ctl |
| Date: | 2013-12-05 14:39:41 |
| Message-ID: | 52A0902D.6020501@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-12-05 14:40:33 | Re: More legacy code: pg_ctl |
| Previous Message | Antonin Houska | 2013-12-05 14:36:50 | Re: Backup throttling |