| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | 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 14:58:39 |
| Message-ID: | 20151002145839.GZ2573@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
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.
Thanks for your continued testing!
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| committs.patch | text/x-diff | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-10-02 18:43:41 | Re: max_worker_processes on the standby |
| Previous Message | Michael Paquier | 2015-10-02 04:11:03 | Re: storage.sgml mentioning htup.h when referring to HeapTupleHeaderData |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-10-02 15:21:11 | Re: What is the extent of FDW join pushdown support in 9.5? |
| Previous Message | Alexander Korotkov | 2015-10-02 14:44:46 | Re: WIP: Rework access method interface |