Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi,

Not sure if I missed a setting a something in v1, please let me know if that's the case...

But, I was wondering if v2 is better (or will be) at managing its database size - in particular in regards to db partitions and retention policies?

With about 1,500 flow runs / 100,000 task runs a day, we seem to be accumulating data rather quickly. About 3 months of running on v1 have given us:
```+--------------+-------------+------------------+-------------------+
|table_name    |relation_size|indexes_sizes_size|total_relation_size|
+--------------+-------------+------------------+-------------------+
|log           |15 GB        |9060 MB           |24 GB              |
|task_run      |5765 MB      |17 GB             |23 GB              |
|task_run_state|13 GB        |6308 MB           |19 GB              |
|flow_run      |241 MB       |472 MB            |713 MB             |
|flow_run_state|438 MB       |118 MB            |557 MB             |
+--------------+-------------+------------------+-------------------+```

Yes definitely, there have been huge steps to improve here