# How to handle growing checkpoint blob?

**URL:** <https://forum.langchain.com/t/how-to-handle-growing-checkpoint-blob/4448>\
**Category:** LangGraph\
**Tags:** js-help\
**Created:** [August 27, 2026, 4:12pm UTC](https://forum.langchain.com/t/how-to-handle-growing-checkpoint-blob/4448 "2026-08-27T16:12:40Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![hks](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.langchain.com/hks/32/3492_2.png) [@hks](https://forum.langchain.com/u/hks)\
**Post date:** [August 27, 2026, 4:12pm UTC](https://forum.langchain.com/t/how-to-handle-growing-checkpoint-blob/4448/1 "2026-08-27T16:12:40Z")

</div>

I’m using open-source LangGraph with `PostgresSaver` and `durability: "exit"`.

The `checkpoints` table looks fine for my use case since I’m seeing roughly one checkpoint per chat request. The issue is that `checkpoint_blobs` keeps growing much faster over time.

For people running LangGraph with Postgres in production, how do you usually manage this growth?

Do you periodically delete older blobs/checkpoints after some retention period, keep only the latest N checkpoints per thread, or use another cleanup strategy?

I still want checkpoint durability, but I don’t need unlimited historical checkpoint data for every conversation.

Would appreciate hearing how others handle checkpoint retention and database size in the open-source libraries.

---

_[View the full topic](https://forum.langchain.com/t/how-to-handle-growing-checkpoint-blob/4448)._