Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZFIWH-0003m7-UQ for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jul 2015 08:58:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZFIWH-0003jv-B6 for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jul 2015 08:58:25 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZFIVw-0003Me-Mh for pgsql-docs@postgresql.org; Wed, 15 Jul 2015 08:58:04 +0000 Received: from smtp-auth.no-ip.com ([8.23.224.61] helo=out.smtp-auth.no-ip.com) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZFIVs-0007qW-U2 for pgsql-docs@postgresql.org; Wed, 15 Jul 2015 08:58:03 +0000 X-No-IP: alvh.no-ip.org@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from alvin.alvh.no-ip.org (unknown [92.255.15.69]) (Authenticated sender: alvh.no-ip.org@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id AD559400C05; Wed, 15 Jul 2015 01:57:54 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id 17AAE93E; Wed, 15 Jul 2015 12:57:52 +0400 (SAMT) Date: Wed, 15 Jul 2015 11:57:52 +0300 From: Alvaro Herrera To: Fujii Masao Cc: pgsql-docs Subject: Re: max_worker_processes on the standby Message-ID: <20150715085751.GD2301@postgresql.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org Fujii Masao wrote: > 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. True. Also track_commit_timestamp. Can you add a comment somewhere in CheckRequiredParameterValues(void) that the set of parameters is listed in section such-and-such in the docs, so that next time there's a higher chance that the docs are kept up to date? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs