# رحلتي نحو إعادة صياغة منشورات ضخمة

**URL:** <https://meta.discourse.org/t/my-journey-into-a-massive-posts-rebake-job/84816>\
**Category:** Self-hosting\
**Created:** [8 أبريل 2018، 12:25م UTC](https://meta.discourse.org/t/my-journey-into-a-massive-posts-rebake-job/84816 "2018-04-08T12:25:59Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)\
**Post date:** [11 يوليو 2018، 9:15ص UTC](https://meta.discourse.org/t/my-journey-into-a-massive-posts-rebake-job/84816/21 "2018-07-11T09:15:29Z")

</div>

> [@sam](#):
>
> but it is a bit tricky cause we would need to carry a big list of ids in memory. I wonder if we should amend it so the rake task is resumable?

This is now done via:

[https://github.com/discourse/discourse/commit/536cef86f4d0a3526d33fd3feb54f03bead7fdd4](https://github.com/discourse/discourse/commit/536cef86f4d0a3526d33fd3feb54f03bead7fdd4)

We no longer carry post ids in memory and the rebake task can be resumed by running `posts:rebake_uncooked_posts`.

One caveat here is that the resume task will _not_ rebake posts in reverse order (i.e. the sort order will be id ascending).

---

_[View the full topic](https://meta.discourse.org/t/my-journey-into-a-massive-posts-rebake-job/84816)._