# Getting deadlock errors in logs

**URL:** https://meta.discourse.org/t/getting-deadlock-errors-in-logs/359146
**Category:** Support
**Tags:** activitypub
**Created:** [March 27, 2025, 1:00pm UTC](https://meta.discourse.org/t/getting-deadlock-errors-in-logs/359146 "2025-03-27T13:00:05Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [March 27, 2025, 5:04pm UTC](https://meta.discourse.org/t/getting-deadlock-errors-in-logs/359146/4 "2025-03-27T17:04:06Z")

</div>

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:

```plaintext
discourse(prod)> DiscourseActivityPubActor.where(domain: 'mastodon.social').size
=> 90264

```

Do we absolutely need to update their `available` column on every delivery?

---

_[View the full topic](https://meta.discourse.org/t/getting-deadlock-errors-in-logs/359146)._