| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, oonishitk(at)nttdata(dot)co(dot)jp, pgsql-docs <pgsql-docs(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: max_worker_processes on the standby |
| Date: | 2015-10-02 18:43:41 |
| Message-ID: | CA+Tgmoaqmo-eSyBQu996Lko7AWu-Yij-Tjd1Zi-LM3UJmU2MKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Fri, Oct 2, 2015 at 10:58 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-10-02 18:59:41 | Re: max_worker_processes on the standby |
| Previous Message | Alvaro Herrera | 2015-10-02 14:58:39 | Re: max_worker_processes on the standby |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2015-10-02 18:43:50 | Re: Request for dogfood volunteers (was No Issue Tracker - Say it Ain't So!) |
| Previous Message | Robert Haas | 2015-10-02 18:41:07 | Re: Freeze avoidance of very large table. |