| From: | Stefan Sonnenberg-Carstens <stefan(dot)sonnenberg(dot)carstens(at)gmail(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system |
| Date: | 2020-01-17 09:33:27 |
| Message-ID: | CAJQkx-WhckT2zpD0WbG6uAOvo0rcoaROKX+MJiLScXcP3K997A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Sergei,
as far as I understand these restrictions apply when hot_standby is set to
on AND a recovery.conf is missing.
I can confirm that hot_standby is commented out - is this setting on by
default?
grep hot_standby /etc/postgresql/10/main/postgresql.conf
#hot_standby = on # "off" disallows queries during
recovery
#hot_standby_feedback = off # send info from standby to prevent
Cheers
Am Fr., 17. Jan. 2020 um 08:58 Uhr schrieb Sergei Kornilov <sk(at)zsrv(dot)org>:
> Hello
>
> No, this is intended and documented behavior:
> https://www.postgresql.org/docs/10/hot-standby.html#HOT-STANDBY-ADMIN
> max_worker_processes must be at least the same as on primary. It is
> because exactly of our technical connection between recovery and the number
> of backends.
>
> regards, Sergei
>
--
Stefan Sonnenberg-Carstens
IT Ingenieur
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Oleksandr Shulgin | 2020-01-17 08:05:27 | Re: libpq parameter parsing problem |