Re: max_worker_processes on the standby
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: oonishitk@nttdata.co.jp, pgsql-docs <pgsql-docs@postgresql.org>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2015-10-02T14:58:39Z
Lists: pgsql-hackers, pgsql-docs
Attachments
- committs.patch (text/x-diff) patch
- (unnamed) (text/plain)
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
Commits
-
Cleanup commit timestamp module activaction, again
- 68cc162e454a 9.5.0 landed
- 531d21b75ff6 9.6.0 landed
-
Code review for transaction commit timestamps
- 6b61955135e9 9.6.0 cited