Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dQeLW-0006yx-NC for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Jun 2017 18:39:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dQeLV-0000jy-HJ for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Jun 2017 18:39:17 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dQeLU-0000jn-LT for pgsql-hackers@postgresql.org; Thu, 29 Jun 2017 18:39:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dQeLS-000722-DD for pgsql-hackers@postgresql.org; Thu, 29 Jun 2017 18:39:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v5TId9MQ006103; Thu, 29 Jun 2017 14:39:09 -0400 From: Tom Lane To: Jeff Janes cc: Andres Freund , Michael Paquier , PostgreSQL mailing lists Subject: Re: Reducing pg_ctl's reaction time In-reply-to: References: <18520.1498508356@sss.pgh.pa.us> <20170626202356.qybnpn5li2ke4ioc@alap3.anarazel.de> <18890.1498508760@sss.pgh.pa.us> <20170626203347.6efkdwiadyt33edy@alap3.anarazel.de> <19812.1498510147@sss.pgh.pa.us> <20170626205853.ezhnmxpotdy3wokm@alap3.anarazel.de> <15166.1498512630@sss.pgh.pa.us> <20170626213414.ejcesidei2hv4h5x@alap3.anarazel.de> <15732.1498513083@sss.pgh.pa.us> <20170626215018.2fudv2aha5rkkg4r@alap3.anarazel.de> <17327.1498515236@sss.pgh.pa.us> <15323.1498589958@sss.pgh.pa.us> Comments: In-reply-to Jeff Janes message dated "Thu, 29 Jun 2017 10:19:46 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6101.1498761549.1@sss.pgh.pa.us> Date: Thu, 29 Jun 2017 14:39:09 -0400 Message-ID: <6102.1498761549@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Jeff Janes writes: > In the now-committed version of this, the 'pg_ctl start' returns > successfully as soon as the server reaches a consistent state. Which is OK, > except that it does the same thing when hot_standby=off. When > hot_standby=off, I would expect it to wait for the end of recovery before > exiting with a success code. Um, won't it be waiting forever with that definition? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers