From: Jerry Sievers <gsievers19@comcast.net>
To: OndYej Svtlík <osvetlik@flexibee.eu>
Cc: pgsql-admin@postgresql.org
Subject: Re: Very long startup after crash with no message in log
Date: Thu, 05 May 2016 12:55:17 -0500
Message-ID: <86oa8k4cfu.fsf@jerry.enova.com> (raw)
In-Reply-To: <572B69D9.5060202@flexibee.eu>
References: <572B69D9.5060202@flexibee.eu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
OndYej Svtlík <osvetlik@flexibee.eu> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gsievers19@comcast.net, osvetlik@flexibee.eu
Subject: Re: Very long startup after crash with no message in log
In-Reply-To: <86oa8k4cfu.fsf@jerry.enova.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox