Ilnur Khanov wrote:
> For me, when I saw "FATAL: the database system is starting up", nothing else hasn't been working: pgAdmin, psql,
businessapps.
"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
andmanually 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
