Re: Very long startup after crash with no message in log

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: OndYej Svtlík <osvetlik(at)flexibee(dot)eu>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Very long startup after crash with no message in log
Date: 2016-05-05 17:55:17
Message-ID: 86oa8k4cfu.fsf@jerry.enova.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

OndYej Svtlík <osvetlik(at)flexibee(dot)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(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Rob Cowell 2016-05-05 20:55:46 Error in log file after database crash
Previous Message Ondřej Světlík 2016-05-05 15:57:30 Re: Autovacuum of pg_database