Another update, after a few days of normal usage.
After the initial spike - I wonder what was going on and I was afraid we wouldn’t have been any closer to a solution - something worked. We don’t know if it was data pruning, updating to PSQL15 or updating to Discourse 2026.1.0, but at least the issue is solved for now.
Thanks again.