Hello. I can't say why this tip worked, but I can say you that you shouldn't bother about the "FATAL: the database system is starting up" message: PgSQL routinely displays this message when starting up. "FATAL" is called "gravity", that is to say it describes the importance of the following message. "FATAL" is the highest importance and, indeed, knowing if your database is up, or not, is of the highest importance, but it is not a fatal error. Regards. Le jeudi 07 décembre 2017 à 10:49 +0500, Ilnur Khanov a écrit : > Hi, > > There is a standalone server with Postgresql 9.6.3 on Windows 2016 > Server. > > I had been faced with "FATAL: the database system is starting up" > after disk failure. This mailing list helped me to solve issue by > setting "hot_standby = on" in postgresql.conf. > But I can't fully understand why it had worked. > > Comments in conf says, that the setting has to be ignored in my case: > === > # - Standby Servers - > # These settings are ignored on a master server. > hot_standby = on # "on" allows queries during > recovery > # (change requires restart) > === > > But it is standalone installation, not slave, there is no > replication. Though there is no recovery.conf and any sign of pending > recovery nor in log, nor in postgres.exe output with debug level 5. > > Why setting "hot_standby = on" had helped me with "FATAL: the > database system is starting up" error on standalone server? Any > ideas? > -- David Guyot Administrateur système / Sysadmin Europe Camions Interactive / Stockway Moulin Collot F-88500 Ambacourt Tél : +33 (0)3 29 30 47 85
Attachment:
signature.asc
Description: This is a digitally signed message part
