Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ayLRl-00028l-Jh for pgsql-admin@arkaria.postgresql.org; Thu, 05 May 2016 15:44:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ayLRl-00034m-3C for pgsql-admin@arkaria.postgresql.org; Thu, 05 May 2016 15:44:13 +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 1ayLQ4-0000dx-2Y for pgsql-admin@postgresql.org; Thu, 05 May 2016 15:42:28 +0000 Received: from mail-wm0-x22d.google.com ([2a00:1450:400c:c09::22d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ayLPw-0000Qi-Io for pgsql-admin@postgresql.org; Thu, 05 May 2016 15:42:27 +0000 Received: by mail-wm0-x22d.google.com with SMTP id g17so34446859wme.1 for ; Thu, 05 May 2016 08:42:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flexibee-eu.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=ZEJ+SJ185Exhr56iULLbFOuqC6FTj2qNT8mXgpzNe5k=; b=hJkR1VaEC5v3FRDOho6LBXbvew4eVAf32CM03qz9geg15ke/wC6hgxL2uGeMVHjFyN PrnKaIdphtO796DQfqNSaDUmUZS8FEo1Z3HDsYQTY8zF7ERHm/871SH+Pht+Ttq/x/Ev ZvflvwkEC73fTaysTz4YUytecfV0dFnmURtevBLqRmzhxmkPzxiKBKMrDiDpjFgLw7L9 IkLzpTlGuehb9W96tVDUr73vt1Xxqmbqrc3m+BfTC0OLKAYI4qfAgst6lb0gnfYSyuJc XJTbg3Ki6qDVcBPNc31SSbjIraF0/HOk4eQMwQ+j/t159s7xO4noYUgfRhXGrRCBRewP mtfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=ZEJ+SJ185Exhr56iULLbFOuqC6FTj2qNT8mXgpzNe5k=; b=ZmmNRoEY3xGwyNLt6aQVUJIlO9CflH7S6A/b11wzaWXj0QRYy4upnzA2N5Yam/8vka xtLRek/sSwVz+m2P6gny8N8Q/3yhuGtrVgOegSTAIsHYWsVYYZowCeNkp7PY5Xb/xeOJ Qu6IqJ5K1Zaul1P+3EwttpwokBtl4qjxp9KYUsRHjU1zqKYAWy3i2PzysYMCPI7e8+lU Zxo35u+4u8Ng+tX+WvIV/wPbO7HRYcNse8k9y4w8lHcP+hd2Xj9Qman1DCy12n6Q9Uj1 G00fbPw7lkiBDnf3jwUeBGiTv32nKD3H9WqWnXnF+5ibDv9cGUuJmZ+MLeCrou0x+59T 2LLg== X-Gm-Message-State: AOPr4FVSdkPD70a1fKD4y0EiH8g3AhnGbz9raw9ivKBo5TwywDtO1lK5FsGN9pT49FPYC7mE X-Received: by 10.194.81.106 with SMTP id z10mr14895885wjx.163.1462462938250; Thu, 05 May 2016 08:42:18 -0700 (PDT) Received: from osvetlik-nb.localdomain ([88.208.120.47]) by smtp.gmail.com with ESMTPSA id 63sm3770642wmz.5.2016.05.05.08.42.17 for (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 May 2016 08:42:17 -0700 (PDT) To: pgsql-admin@postgresql.org From: =?UTF-8?B?T25kxZllaiBTdsSbdGzDrWs=?= Subject: Very long startup after crash with no message in log Message-ID: <572B69D9.5060202@flexibee.eu> Date: Thu, 5 May 2016 17:42:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.6 (--) 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 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? Thank you, Ondřej -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin