Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ayNUy-0000XK-8z for pgsql-admin@arkaria.postgresql.org; Thu, 05 May 2016 17:55:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ayNUx-0007nU-Qi for pgsql-admin@arkaria.postgresql.org; Thu, 05 May 2016 17:55:39 +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 1ayNUx-0007nO-CY for pgsql-admin@postgresql.org; Thu, 05 May 2016 17:55:39 +0000 Received: from resqmta-ch2-03v.sys.comcast.net ([2001:558:fe21:29:69:252:207:35]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ayNUs-0003Jo-GU for pgsql-admin@postgresql.org; Thu, 05 May 2016 17:55:38 +0000 Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by comcast with SMTP id yNR3a0uyXLCmUyNUmajndT; Thu, 05 May 2016 17:55:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1462470928; bh=7DMnEOz+mIrReoZRlrbk9m72ZCyFAM0yIiHgCRA2q6g=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=VR+XRSJpjPz8Dy35pg5QWtH4sXKpcKX3pkEX6eNMqIB5d+F0NGebcdsQ2lsC2i9d4 uF/fTEzucQ/fWG6r+cI2vrNmi+5EA6M3rfLjBwVZNr6Fdqtv8gUi9mjHm+HruDA3Lm OjVCUFGn6bEh2ALQ9Y6a5E0Ez568in9Ll3x3ks5RKAMzMAX5zMRE9nXpxgxzZp5KiE LgWSiKwkbrt9wZK9mprCELtT11UUxHIu1/kjATqYqP5Jer5NX0oebhbGaDbpM9sfUs ik7lGCWRpKAcAUOo7hzzYa1tRYhsf97CcoCF05MRjZOs+PabIGw76RVBWm8lkhNGWW xJ5s7+imsGdug== Received: from jerry.enova.com ([12.187.116.132]) by resomta-ch2-20v.sys.comcast.net with comcast id qhvH1s00Q2rU9cC01hvKzs; Thu, 05 May 2016 17:55:26 +0000 Received: by jerry.enova.com (Postfix, from userid 1001) id 679C1740207; Thu, 5 May 2016 12:55:17 -0500 (CDT) From: Jerry Sievers To: OndYej =?iso-8859-1?Q?Sv=1Btl=EDk?= Cc: pgsql-admin@postgresql.org Subject: Re: Very long startup after crash with no message in log References: <572B69D9.5060202@flexibee.eu> Date: Thu, 05 May 2016 12:55:17 -0500 In-Reply-To: <572B69D9.5060202@flexibee.eu> (OndYej Sv's message of "Thu, 5 May 2016 17:42:17 +0200") Message-ID: <86oa8k4cfu.fsf@jerry.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -3.5 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org OndYej Svtlík writes: > Hello again, > > last night we came across another unpleasant behaviour. I managed to > crash the cluster and the next start took really long (about 4 > hours). Even in single mode with -d1 there was no message telling us > what's going on. We used lsof and found out that the process opens > each database and performs some operation which takes up to a few > seconds (with almost 6k databases). It would be really nice to tell > the user what's going on. Or is there a configuration option which > will enable such logging, perhaps? Have a look at log_min_messages. > Thank you, > > OndĹ™ej -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin