Re: [DOCS] max_worker_processes on the standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [DOCS] max_worker_processes on the standby
Date
Msg-id CA+Tgmoaqmo-eSyBQu996Lko7AWu-Yij-Tjd1Zi-LM3UJmU2MKQ@mail.gmail.com
Whole thread Raw
In response to Re: [DOCS] max_worker_processes on the standby  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [DOCS] max_worker_processes on the standby  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Oct 2, 2015 at 10:58 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Fujii Masao wrote:
>
>> What happens if pg_xact_commit_timestamp() is called in standby after
>> track_commit_timestamp is disabled in master, DeactivateCommitTs() is
>> called and all commit_ts files are removed in standby? I tried that case
>> and got the following assertion failure.
>
> Ah.  So the standby needs to keep the module activated if it's enabled
> locally, even when it receives a message that the master turned it off.
> Here's a patch.

The standby can have the feature enabled even though the master has it
disabled?  That seems like it can only lead to heartache.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Freeze avoidance of very large table.
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Request for dogfood volunteers (was No Issue Tracker - Say it Ain't So!)