Eric Wong writes:
> Kyle Meyer wrote:
>>
>> Oops, the few times I've used --reindex I don't think I've given order
>> much thought. Is it accurate to say that "restart services then
>> --reindex" is the recommended order in general?
>
> Not really. In the distant past (pre-SCHEMA_VERSION=15),
Kyle Meyer wrote:
> Eric Wong writes:
> > Eric Wong wrote:
> >> It requires "public-inbox-index --reindex" to activate;
> >> but PATCH 5/5 makes it safe to upgrade WWW either before
> >> or after --reindex. That means BOFHs can upgrade without
> >> regard to ordering.
> >
> > public-inbox-watch
Eric Wong writes:
> Eric Wong wrote:
>> It requires "public-inbox-index --reindex" to activate;
>> but PATCH 5/5 makes it safe to upgrade WWW either before
>> or after --reindex. That means BOFHs can upgrade without
>> regard to ordering.
>
> public-inbox-watch users will need to restart -watch
Eric Wong wrote:
> It requires "public-inbox-index --reindex" to activate;
> but PATCH 5/5 makes it safe to upgrade WWW either before
> or after --reindex. That means BOFHs can upgrade without
> regard to ordering.
public-inbox-watch users will need to restart -watch before
--reindex, though. D
Actually, the Xapian aspect of it turned out to be easy once
I learned ->set_collapse_key.
Getting the tests and compatibility with existing (pre-upgrade)
inboxes was more work.
It requires "public-inbox-index --reindex" to activate;
but PATCH 5/5 makes it safe to upgrade WWW either before
or aft
