On Mon, Jan 27, 2020, at 9:51 AM, Egoitz Aurrekoetxea via Info-cyrus wrote:Just for having it slightly clearer… When you upgrade the Cyrus version and the version you are upgrading to is a too close one… for instance from 3.0.8 to 3.0.13 and you see the Cyrus version is the same for users mail folders, 13 in both… is it needed to launch (or recommended for some reason) the final upgrade commands :reconstruct -V maxctl_conversationsdb -b -rquota -f
As long as you're looking at 3.x.x and higher*, then if it's a stable release (where only the third number has changed, e.g. 3.0.8->3.0.13) you shouldn't need to. We don't do big world-breaking/data-format-changing changes in stable releases like this.
That said, we might have fixed a bug between the versions, and your existing data might be bad due to the bug that was fixed, and you might need to run commands like these after upgrading to the fixed version to repair the bad data. If I know this is the case, I'll say so in the release notes (so check those, including for the intermediate releases if you're skipping over some). But I might not know until someone upgrades and reports that they needed to do it.
So, if it doesn't say you need to do it, you probably don't need to do it. But if you don't do it, and things like quota or conversations seem weird after the upgrade, try these sort of commands. And if it fixes it, let us know (on the mailing list or a github issue) so we can retcon the release notes to mention it for the next person. :)
* For people looking at 2.5 and earlier, this pattern doesn't necessarily hold, and I don't know enough about those older versions to provide general advice. If in doubt, ask the mailing list, and if you can run a recent version (that's closer to what's in Fastmail's organisational memory), that's your best bet ;)
Cheers,
ellie
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
