|From:||Stefan Sonnenberg-Carstens <stefan(dot)sonnenberg(dot)carstens(at)gmail(dot)com>|
|To:||Sergei Kornilov <sk(at)zsrv(dot)org>|
|Subject:||Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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
Then, indeed, this is not a bug.
Thank you for this explanation and your help!
Am Fr., 17. Jan. 2020 um 10:45 Uhr schrieb Sergei Kornilov <sk(at)zsrv(dot)org>:
> > 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:
> ArchiveRecoveryRequested is set if we found recovery.conf (see
> > I can confirm that hot_standby is commented out - is this setting on by
> Yes, in postgresql 10 and newer.
> regards, Sergei
|Next Message||PG Bug reporting form||2020-01-17 12:42:19||BUG #16216: the result of to_date function with negative year number not same as BC year number|
|Previous Message||Sergei Kornilov||2020-01-17 09:45:36||Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system|