From: | Ilnur Khanov <khanov(dot)i(at)gmail(dot)com> |
---|---|
To: | 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 08:35:35 |
Message-ID: | CAN+PxfQjAC_GiSZ7WHZxsYNQTx0f=k8C2k3HMhRifsWKYHPVQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
For me, when I saw "FATAL: the database system is starting up", nothing
else hasn't been working: pgAdmin, psql, business apps.
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.
By "PostgreSQL is still in some strange mode" I mean that setting "hot_standby
= off" returns "the-FATAL-error" and nothing works then.
From | Date | Subject | |
---|---|---|---|
Next Message | Mayank Gupta - Network | 2017-12-07 09:50:31 | Need help in making the schema name case insensitive. |
Previous Message | David Guyot | 2017-12-07 08:11:58 | Re: "FATAL: the database system is starting up" and hot_standby = on |