告诉HN：Mattermost "升级"到v11 强制限制10,000条UI消息
我自2019年以来一直自托管Mattermost（最初是为了逃避Slack对家庭聊天的保留限制；包括物流、照片和随机历史）。让他们都使用Slack是一个巨大的障碍，然后再将他们迁移到Mattermost又是另一个挑战。
今天早上，我按照Mattermost的明确弃用通知和建议，将我们长期运行的Omnibus安装从v10.9.1升级到v11。
升级过程非常顺利：
- Postgres迁移正常
- 数据仍然存在于数据库中
- 服务在几分钟内恢复
重启后，用户界面显示：
“已达到10,000条消息限制。2023年5月16日之前发送的消息被隐藏。”
澄清一下：没有任何地方执行DELETE FROM。所有行仍在PostgreSQL中。这个限制仅在用户界面/视图层生效，且在“升级”后追溯适用。
在此之前检查了：
- Omnibus弃用公告
- v11升级指南
- 管理控制台的提示/链接
没有提到就地升级会对现有数据激活严格的可见性限制。第一次提示是在重启后的运行实例中。
截至目前（2026年1月12日 13:37）：
- https://mattermost.com/pl/mattermost-entry-limits（应用内链接到限制）404（页面未找到）
- https://mattermost.com/pricing/（也是一个应用内链接）只有“联系销售”，没有列出限制（或价格）。
- https://docs.mattermost.com/administration-guide/manage/product-limits.html，使用Kagi找到这个，没有提到消息限制。
我乐意为支持的软件付费。问题在于自托管和自管理数据库上意外的强制执行。升级路径悄然将历史记录变成了一个需要许可的功能，而在升级文档中没有提前警告。
目前：
我们将v11实例保持在线（安全，当前消息正常流动）。系统控制台和仪表板加载不正确，可能是由于消息限制，也可能是其他问题。
我在考虑某种rsync + 当前可见历史的静态HTML归档 + 数据库转储以便离线搜索。我担心未来的政策变化可能会进一步限制访问，欢迎任何建议。
我主要发布这个内容是为了警告其他长期使用Omnibus的用户（小组、家庭、爱好服务器），他们即将升级，可能没有预料到视图限制会追溯生效。
如果您的安装早于限制引入并且消息超过10,000条，请先在测试环境中进行升级——或者假设文档在执行时间上是不完整的。不要指望在论坛中获得帮助，最后一条帖子（在我今天之前）是2025年10月的，版主指向了Gitlab Omnibus线程，该线程没有提供关于消息限制的详细信息或回答其他问题。
我很好奇其他人在v11“升级”中是否遇到了意外，以及是否有人有任何建议。
查看原文
I've self-hosted Mattermost since 2019 (originally to escape Slack’s retention limits for family chat; logistics, photos, random history). It was a huge hurdle getting them all on Slack, and then moving them again to Mattermost.<p>This morning, I upgraded our long-running Omnibus install from v10.9.1 → v11, following Mattermost's explicit deprecation notice[0] and recommendation to switch to standard Binary/Docker/k8s/etc deployment.<p>Upgrade went cleanly:<p>Postgres migration fine
Data still present in DB
Service came back up in minutes<p>Post-restart the UI shows:
“10,000-message limit reached. Messages sent before May 16, 2023 are hidden.”
Clarification: no DELETE FROM anywhere. All rows still in PostgreSQL. The limit is UI/view-layer only, retroactively applied after "upgrade".<p>Checked beforehand:<p>- Omnibus deprecation announcement [0]
- v11 upgrade guide [4]
- Admin console nags/links<p>None mentioned that an in-place upgrade would activate hard visibility caps on pre-existing data. First indication was the running instance after restart.<p>Currently (as of 2026-01-12_1337):<p>- https://mattermost.com/pl/mattermost-entry-limits (In-App Link to Limits) [1] 404s (Page not found)
- https://mattermost.com/pricing/ (also an in-app link) [2] only has “Contact Sales”, no enumerated limits (or prices).
- https://docs.mattermost.com/administration-guide/manage/product-limits.html [3], used Kagi to find this, no mention of message limits<p>I'm happy to pay for supported software. The friction is the surprise enforcement on self-hosted + self-managed DB. Upgrade path quietly turned history into a licensed feature without forewarning in the upgrade docs.<p>For now:<p>We're leaving the v11 instance up (secure, current messages flow normally). The system console and dashboard aren't loading correctly, possibly due to the message limits, possibly due to other issues.<p>I'm thinking some sort of rsync + static HTML archive of current visible history + DB dump for offline search. I'm afraid future policy changes could further gate access, and would love recommendations.<p>Posting mostly as warning to other long-running Omnibus users (small groups, families, hobby servers) who are about to upgrade and may not expect the view limit to kick in retroactively.<p>If your install predates the limit introduction and has >10k messages, test upgrade in staging first—or assume the docs are incomplete on enforcement timing. Don't expect to get help in the forum [5], the last post (before mine today) is from October 2025 and the moderator directed to the Gitlab Omnibus thread which doesn't provide details on message limits or answer the other questions.<p>Curious if others hit surprises on the v11 "upgrade", and if anyone has any suggestions.<p>[0] https://github.com/mattermost/mattermost-omnibus
[1] https://mattermost.com/pl/mattermost-entry-limits
[2] https://mattermost.com/pricing/
[3] https://docs.mattermost.com/administration-guide/manage/product-limits.html
[4] https://docs.mattermost.com/deployment-guide/server/deploy-linux.html
[5] https://forum.mattermost.com/t/clarification-needed-for-the-upgrade-to-v11/25344