# What is writing so much postgres disk space?

**URL:** <https://forum.thegraph.com/t/what-is-writing-so-much-postgres-disk-space/3380>\
**Category:** Questions & Feedback\
**Tags:** indexer, subgraph-devs\
**Created:** [May 29, 2022, 9:01am UTC](https://forum.thegraph.com/t/what-is-writing-so-much-postgres-disk-space/3380 "2022-05-29T09:01:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cinjon](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/cinjon/32/863_2.png) [@cinjon](https://forum.thegraph.com/u/cinjon)\
**Post date:** [May 29, 2022, 9:01am UTC](https://forum.thegraph.com/t/what-is-writing-so-much-postgres-disk-space/3380/1 "2022-05-29T09:01:09Z")

</div>

I ran into an issue where I ran out of postgres disk space. I am using Docker with image graphprotocol/graph-node:v0.25.0. I’m otherwise doing what I perceive to be fairly tame operations saving data while running the node and being strict about what I’m saving. Further, my graph-node service and my postgres service are on different machines, and it’s the latter that ran out of disk.

My understanding is that I am streaming blocks as they come in, taking actions on them according to the subgraph’s .ts files, and then moving on. Is this wrong and my graph-node is actually indexing every block’s data while running this service? If so, is there a way to make that more sparse? I would expect that, once the node has read a block, that it would then move on to the next one and not save it. Where can I find information in the docs on what exactly is being saved by the graph node to postgres?

Thanks!

---

<div class="post-metadata">

**Author:** ![cindyforcia](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/cindyforcia/32/562_2.png) [@cindyforcia](https://forum.thegraph.com/u/cindyforcia)\
**Post date:** [June 1, 2022, 9:59am UTC](https://forum.thegraph.com/t/what-is-writing-so-much-postgres-disk-space/3380/2 "2022-06-01T09:59:12Z")

</div>

Can you share the error code?

---

<div class="post-metadata">

**Author:** ![DataNexus](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.thegraph.com/datanexus/32/1830_2.png) [@DataNexus](https://forum.thegraph.com/u/DataNexus)\
**Post date:** [June 8, 2022, 6:19pm UTC](https://forum.thegraph.com/t/what-is-writing-so-much-postgres-disk-space/3380/3 "2022-06-08T18:19:16Z")

</div>

Just a guess from experience, check your arrays. If you have a table with millions of records and there is 1 record with many values in the array, it will cause every record to LOB.