Job exception: PG::TRDeadlockDetected: ERROR: deadlock detected DETAIL: Process 29659 waits for ShareLock on transaction 892416679; blocked by process 29650. Process 29650 waits for ShareLock on transaction 892416541; blocked by process 29659. HINT: See server log for query details. CONTEXT: whi…

Hmm, that doesn’t seem to fix the issue unfortunately @angus . There’s a lot of actors, possibly, in the DB, and the batching is still insufficient. On meta, for example, there are 90k+ rows in that model: discourse(prod)> DiscourseActivityPubActor.where(domain: 'mastodon.social').size => 90264 Do…

I see. Hopefully this, together with the previous changes, will address it: https://github.com/discourse/discourse-activity-pub/pull/204

Getting deadlock errors in logs

Support

angus (Angus McLeod) March 27, 2025, 3:06pm 3

This should address it

https://github.com/discourse/discourse-activity-pub/pull/203

Topic		Replies	Views
2 emails rejected by 2026.4.0-latest ( 5f0d95e1f1 ) Self-hosting mail-receiver	4	108	April 15, 2026
[2.4.0beta9] ActiveRecord::Deadlocked (PG::TRDeadlockDetected: ERROR: deadlock detected) Support	3	1644	December 24, 2019
'Updating Last Seen' and 'hijack topics timings' and 'Track Visit' is still running after 90 seconds Support	11	1031	October 9, 2024
Load average ×2 since last upgrade Bug activitypub	5	216	December 22, 2025
Remapping fails due to deadlock Support	7	526	November 25, 2020

Getting deadlock errors in logs

Related topics