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

Hello ! I'm using Prefect with PostgreSQL and some of the tables are becoming quite huge (like `log`). I was wondering why deleting a Flow Run (using the API) doesn't delete the associated entries in the `log` table? :arrow_down:

I ran this query to discover that:
```SELECT
    *
FROM
    log l
WHERE
    NOT EXISTS (
        SELECT
            *
        FROM
            task_run tr
        WHERE
            tr.id = l.task_run_id
    );```

Is there a set of Export/Clean-Up scripts that Prefect can share on how to prune old flow runs and there related tables?

Hi there, we have a github issue around resolving that, so it may be a good idea to add any additional thoughts there:
<https://github.com/PrefectHQ/prefect/issues/10000>

Hello <@U03E9RV7BDM>! Is it something that I can do to help about this? I have to admit that having this PR merged could be very helpful to help maintenance

That’s actually an issue not a PR :disappointed: We generally take contributors though

<@U03E9RV7BDM> I see this issue has not been prioritized, does prefect have any documentation on self-hosted recommended clean up tasks.  I have noticed that when you delete a flow_run it does clean up some of the other tables.  I would love to know which ones are and are not cleaned up so we could write a script archive and purge our db

Hi Gregory, I don’t think that we do. Feel free to create an issue for it :)