Re: max_worker_processes on the standby - Mailing list pgsql-docs

From Petr Jelinek
Subject Re: max_worker_processes on the standby
Date
Msg-id 55F8DE22.5090602@2ndquadrant.com
Whole thread Raw
In response to Re: max_worker_processes on the standby  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-docs
On 2015-09-03 15:03, Fujii Masao wrote:
> On Sat, Aug 8, 2015 at 11:02 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> There's no existing precedent for a feature that lets the standby be
>> different from the master *in any way*.  So I don't see why we should
>> start here.  I think the reasonable definition is that the GUC
>> controls whether the master tries to update the SLRU (and generate
>> appropriate WAL records, presumably).  The standby should not get a
>> choice about whether to replay those WAL records.
>
> +1
>
> I added this to the 9.5 open item list.
>

I see I forgot to send patch for this, so here it is. It just removes
the on start check for track_commit_timestamp being same in config and
control file.

--
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-docs by date:

Previous
From: "Charles Clavadetscher"
Date:
Subject: Re: Missing COMMENT ON POLICY - update
Next
From: "Amir Rohan"
Date:
Subject: Docs claim that "select myTable.*" wildcard won't let you assign column names