# PostgreSQL runaway IO

**URL:** <https://meta.discourse.org/t/postgresql-runaway-io/91516>\
**Category:** Self-hosting\
**Created:** [3 juli 2018 om 21:59 UTC](https://meta.discourse.org/t/postgresql-runaway-io/91516 "2018-07-03T21:59:01Z")\
**Posts on this page:** 1\
**Showing post:** 34

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [31 juli 2018 om 18:22 UTC](https://meta.discourse.org/t/postgresql-runaway-io/91516/34 "2018-07-31T18:22:48Z")

</div>

Denormalizing & pruning the post\_timings table also came up during GDPR work, and I wasn’t really able to come up with a coherent plan of action there either. The (user, post, duration) really does get used individually and without a solid time cutoff, so you can’t just truncate the table and expect that you’re only purging old entries.

---

_[View the full topic](https://meta.discourse.org/t/postgresql-runaway-io/91516)._
