@feld It certainly did not do that with Pleroma's configuration at least. There are more cache misses, held locks and increased reads in Postgres. Unless there was a change in Pleroma somewhere between 2.6.3 and the Oban bump commit that would cause exactly this, which is unlikely I think.