pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Very long startup after crash with no message in log 2+ messages / 2 participants [nested] [flat]
* Very long startup after crash with no message in log @ 2016-05-05 15:42 Ondřej Světlík <osvetlik@flexibee.eu> 2016-05-05 17:55 ` Re: Very long startup after crash with no message in log Jerry Sievers <gsievers19@comcast.net> 0 siblings, 1 reply; 2+ messages in thread From: Ondřej Světlík @ 2016-05-05 15:42 UTC (permalink / raw) To: pgsql-admin 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Very long startup after crash with no message in log 2016-05-05 15:42 Very long startup after crash with no message in log Ondřej Světlík <osvetlik@flexibee.eu> @ 2016-05-05 17:55 ` Jerry Sievers <gsievers19@comcast.net> 0 siblings, 0 replies; 2+ messages in thread From: Jerry Sievers @ 2016-05-05 17:55 UTC (permalink / raw) To: OndYej Svtlík <osvetlik@flexibee.eu>; +Cc: pgsql-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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2016-05-05 17:55 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2016-05-05 15:42 Very long startup after crash with no message in log Ondřej Světlík <osvetlik@flexibee.eu> 2016-05-05 17:55 ` Jerry Sievers <gsievers19@comcast.net>
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