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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: stefan(dot)sonnenberg(dot)carstens(at)gmail(dot)com
Subject: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
Date: 2020-01-17 07:22:10
Message-ID: 16215-36f9d5763709c11c@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16215
Logged by: Stefan Sonnenberg-Carstens
Email address: stefan(dot)sonnenberg(dot)carstens(at)gmail(dot)com
PostgreSQL version: 10.11
Operating system: Linux
Description:

I tried to restore a binary backup (basebackup + WAL archives) onto a
smaller machine.
During restore the following log message was issued:

2020-01-17 07:14:20.524 UTC [19274] FATAL: hot standby is not possible
because max_worker_processes = 2 is a lower setting than on the master
server (its value was 8)
2020-01-17 07:14:20.526 UTC [19273] LOG: startup process (PID 19274) exited
with exit code 1
2020-01-17 07:14:20.526 UTC [19273] LOG: aborting startup due to startup
process failure
2020-01-17 07:14:20.541 UTC [19273] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.

The workaround was to raise the number of max_worker_process for the
recovery process to work and lowering it afterwords.

This seems to be a bug to me, as I don't see a technical connection between
these settings for the restore to be successful.

Cheers

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sergei Kornilov 2020-01-17 07:58:52 Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
Previous Message Michael Paquier 2020-01-17 06:29:45 Re: libpq parameter parsing problem