# Long runtime moving posts / timeout errors

**URL:** <https://meta.discourse.org/t/long-runtime-moving-posts-timeout-errors/351345>\
**Category:** Product Support\
**Created:** [February 9, 2025, 4:09pm UTC](https://meta.discourse.org/t/long-runtime-moving-posts-timeout-errors/351345 "2025-02-09T16:09:09Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [February 9, 2025, 6:43pm UTC](https://meta.discourse.org/t/long-runtime-moving-posts-timeout-errors/351345/4 "2025-02-09T18:43:24Z")

</div>

> [@Thorsten](#):
>
> Is it possible that the skipped database update causes our performance issues?

Probably not.

> [@Thorsten](#):
>
> Is there an easy way to check if the database indexes and statistics are correct?

You can do the vacuum and reindex commands suggested in the PG update topic at any time.

---

_[View the full topic](https://meta.discourse.org/t/long-runtime-moving-posts-timeout-errors/351345)._