Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system

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(at)zsrv(dot)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