|
From: | Vladimir Sementsov-Ogievskiy |
Subject: | Re: [PATCH] replication: compile out some staff when replication is not configured |
Date: | Fri, 14 Apr 2023 12:50:34 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 |
On 14.04.23 04:24, Zhang, Chen wrote:
So, if I want to have an option to disable all COLO modules, do you mean it should be additional --disable-colo option? Or better keep one option -- disable-replication (and, maybe just rename to to --disable-colo)?I think keep the option --disable-replication is enough. Generally speaking, these three modules do not belong to COLO, It has been decoupled at the time of design. Instead, COLO is formed when these three modules are used in combination.
But it's not enough to me, I want to have a possibility to not build the subsystem I don't need. -- Best regards, Vladimir
[Prev in Thread] | Current Thread | [Next in Thread] |