Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16215: Restore failes if number of workers inpostgresql.conf is lower than on source system - Mailing list pgsql-bugs

From Stefan Sonnenberg-Carstens
Subject Re: BUG #16215: Restore failes if number of workers inpostgresql.conf is lower than on source system
Date
Msg-id CAJQkx-WNtrRnsG7+2jC0tCbOmqyMGdUMdYt0EzqgM6B68TcPzA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-bugs
Tree view
Sure, during restore the recovery.conf is present (as I create it to be able to do the restore).
After setting the parameter hot_standby explicitly to off, I can confirm that it is no longer required to have higher values as on the source system.

Ok, It would be great to have this default as a comment in the postgresql.conf that is created during cluster init as for many other parameters.
Then, indeed, this is not a bug.

Thank you for this explanation and your help!

Cheers


Am Fr., 17. Jan. 2020 um 10:45 Uhr schrieb Sergei Kornilov <sk@zsrv.org>:
Hello

> as far as I understand these restrictions apply when hot_standby is set to on AND a recovery.conf is missing.

When hot_standby is set to on AND a recovery.conf is PRESENT
Here is: https://github.com/postgres/postgres/blob/REL_10_STABLE/src/backend/access/transam/xlog.c#L6185
ArchiveRecoveryRequested is set if we found recovery.conf (see readRecoveryCommandFile)

> I can confirm that hot_standby is commented out - is this setting on by default?

Yes, in postgresql 10 and newer.

regards, Sergei


--
Stefan Sonnenberg-Carstens
IT Ingenieur

pgsql-bugs by date:

Previous
From: Sergei Kornilov
Date:
Subject: Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
Next
From: PG Bug reporting form
Date:
Subject: BUG #16216: the result of to_date function with negative year number not same as BC year number