Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDt7V-0007wA-RQ for pgsql-general@arkaria.postgresql.org; Thu, 25 May 2017 13:48:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dDt7V-0004qQ-90 for pgsql-general@arkaria.postgresql.org; Thu, 25 May 2017 13:48:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dDt7T-0004ou-R0 for pgsql-general@postgresql.org; Thu, 25 May 2017 13:48:03 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dDt7Q-0001D7-4b for pgsql-general@postgresql.org; Thu, 25 May 2017 13:48:03 +0000 Received: from pro.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v4PDltVO011021; Thu, 25 May 2017 09:47:55 -0400 From: Tom Lane To: y39chen cc: pgsql-general@postgresql.org Subject: Re: Re: Is there possibility btree_redo with XLOG_BTREE_DELETE done between standby_redo and the end of backup In-reply-to: <1495704189413-5963181.post@n3.nabble.com> References: <1495609157661-5963011.post@n3.nabble.com> <2253.1495639128@sss.pgh.pa.us> <2353.1495640833@sss.pgh.pa.us> <1495704189413-5963181.post@n3.nabble.com> Comments: In-reply-to y39chen message dated "Thu, 25 May 2017 02:23:09 -0700" Date: Thu, 25 May 2017 09:47:55 -0400 Message-ID: <15664.1495720075@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org y39chen writes: > We found the panic happened when adding one of our patch. > switch (port->canAcceptConnections) > { > case CAC_STARTUP: > ereport(*LOG*, > (errcode(ERRCODE_CANNOT_CONNECT_NOW), > errmsg("the database system is starting up"))); > break; Did you not absorb the advice given in https://www.postgresql.org/message-id/23381.1494607092@sss.pgh.pa.us ? The above patch is simply an impossibly bad idea. Don't do it. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general