From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Ilnur Khanov <khanov(dot)i(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: "FATAL: the database system is starting up" and hot_standby = on |
Date: | 2017-12-07 17:37:32 |
Message-ID: | 1512668252.2915.17.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ilnur Khanov wrote:
> For me, when I saw "FATAL: the database system is starting up", nothing else hasn't been working: pgAdmin, psql, business apps.
"FATAL" just means that a client connection is terminated.
In this case, because the database is not up.
> Logs has been showing cycles: client connect - worker starts - "the-FATAL-error" -
> worker shutting down with exit code (1). No any informative errors.
>
> I think, database engine is in some sort of recovery mode after crush, but I was
> waiting long enough - no CPU or HDD activity. If it's some sort of warning and waiting for me to check consistency and manually reset this mode flag, but then how to do this?!
>
> More important: now problem is not solved, "hot_standby = on" is just workaround letting query databases.
> But PostgreSQL is still in some strange mode and I don't understand how serious is it and how resolve it correctly.
You cannot modify the database, right?
And "SELECT pg_is_in_recovery();" returns TRUE, right?
Could you show us what is written to the log after a new startup?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Ilnur Khanov | 2017-12-08 04:31:59 | Re: "FATAL: the database system is starting up" and hot_standby = on |
Previous Message | Mayank Gupta - Network | 2017-12-07 13:03:09 | RE: [EXTERNAL] Re: Need help in making the schema name case insensitive. |