Message-ID: <1512634318.2188.3.camel@europecamions-interactive.com>
Subject: Re: "FATAL: the database system is starting up" and hot_standby = on
From: David Guyot <david.guyot@europecamions-interactive.com>
To: pgsql-admin@lists.postgresql.org
Date: Thu, 07 Dec 2017 09:11:58 +0100
In-Reply-To: 
 <CAN+PxfQwWM5j4LvJNV1jERuvLV4x-Oi6w6JKQadPft_AztQBfQ@mail.gmail.com>
References: 
	<CAN+PxfQwWM5j4LvJNV1jERuvLV4x-Oi6w6JKQadPft_AztQBfQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256";
	protocol="application/pgp-signature"; boundary="=-PB2b81MXmvLEnpCrXo8a"
Mime-Version: 1.0
Precedence: bulk


--=-PB2b81MXmvLEnpCrXo8a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=C3=A9cembre 2017 =C3=A0 10:49 +0500, Ilnur Khanov a =C3=A9cri=
t=C2=A0:
> Hi,
>=20
> There is a standalone server with Postgresql=C2=A09.6.3 on Windows 2016
> Server.
>=20
> 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 =3D on" in=C2=A0postgresql.conf.
> But I can't fully understand why it had worked.
>=20
> Comments in conf says, that the setting has to be ignored in my case:
> =3D=3D=3D
> # - Standby Servers -
> # These settings are ignored on a master server.
> hot_standby =3D on			# "on" allows queries during
> recovery
> 					# (change requires restart)
> =3D=3D=3D
>=20
> 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.
>=20
> Why setting "hot_standby =3D on" had helped me with "FATAL: the
> database system is starting up" error on standalone server? Any
> ideas?
>=20
--=20
David Guyot
Administrateur syst=C3=A8me=C2=A0/ Sysadmin
Europe Camions Interactive=C2=A0/ Stockway
Moulin Collot F-88500 Ambacourt
T=C3=A9l=C2=A0: +33 (0)3 29 30 47 85
--=-PB2b81MXmvLEnpCrXo8a
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE3x4z121mNEB/JJ/PgVDjr4mKouAFAloo984ACgkQgVDjr4mK
ouDBMQ//X75s8BwMONrS/y5vqMUCupfXOSV0KmAJ6u4ieCAf01UAT9Xr2NvEtmUn
uYt7M+R0AGyWSCdKsT62R/HOTO9CUJuJfGLBZntIiWYkvAgNlpytkWdmbEeuZMSl
dH6/7jyQFLVn8cnAyCukZOkXw/z8ftZV/igjKV1S/WYIkgHVUrCgFi5flS9d6VdR
lUe1iS/9t8r/pebrYgm814iEpl0OzM2nSXnHN3GN8GmkRaAireBTSvZdVkgtwgYk
JftXxpdl+wJ9ec9sLbK0aR389pdUTZaB0IqOFyLg7m+nfKM8g1roagMJucfpkVnc
noFWqbU9WM4AEk8szT581WxxOMal5NdZnNrALrLHuATM0MwbUjSri6puhFw262Tq
2gWatA7dn8xWe2SYjCz/HwpA/zXlhmTxZo07tPiLUh3t+mx6eO4bsKL37qOeQfya
4Me+DNMJnxBnJNOU1LR4thv6nJjMd2FG8nvzGJi1TugVzvCuuQPdSAwOLejJZnSf
VHbNiL/02QnZHcHtgzmemT69Kx9m2Oh6nNKZPpnNkztA5H0AVHlw3bQQUEcJ54Jp
KdqgloeSr1MPrCs8suFksqIjH6tCVc8fzMH1u0TdQjvWqQ8OGstTs1Lxh+9ap8Vx
sFlwebt7dAPcYyZx2pOfkg3agMIzfKaldnVF2sPc1dMBpSRi+us=
=+553
-----END PGP SIGNATURE-----

--=-PB2b81MXmvLEnpCrXo8a--