max_worker_processes on the standby

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: max_worker_processes on the standby
Date: 2015-07-15 04:38:19
Message-ID: CAHGQGwE48ViDkwybpxjXuf-trC87Ar1jdCHZ+ogtduoo3uvB8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

Hi,

"25.5.3. Administrator's Overview" in the document
-----------------------------------------------------
The setting of some parameters on the standby will need reconfiguration
if they have been changed on the primary. For these parameters,
the value on the standby must be equal to or greater than the value
on the primary. If these parameters are not set high enough then
the standby will refuse to start. Higher values can then be supplied
and the server restarted to begin recovery again. These parameters are:
max_connections
max_prepared_transactions
max_locks_per_transaction
-----------------------------------------------------

I found that the value of max_worker_processes on the standby also
must be equal to or greater than the value on the master. So we should
just add max_worker_processes to this paragraph. Patch attached.

Regards,

--
Fujii Masao

Attachment Content-Type Size
doc.patch text/x-patch 449 bytes

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Alvaro Herrera 2015-07-15 08:57:52 Re: max_worker_processes on the standby
Previous Message Ian Barwick 2015-07-14 03:24:46 Clarification for schema and schema object privileges

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2015-07-15 04:58:58 Re: TABLESAMPLE patch is really in pretty sad shape
Previous Message Kouhei Kaigai 2015-07-15 04:09:56 Re: security labels on databases are bad for dump & restore