Hello Prefect Devs, Is there any reason an on delete cascade delete foreign key relationship from

flow_run.id

to

log.flow_run_id

/

task_run.id

to

log.task_run_id

does not exist?

Theres not a major reason to enforce referential integrity there. For example there isn't a place to retrieve logs individually where it's harmful for their parent run to not exist. On the flip side it's also a big performance hit to enforce the FK on log insert and on also on run deletion via cascade, where every run could have N logs

Thanks @Jake Kaplan We have a self hosted Prefect Database on prod and the logs table in prefect has grown to be larger than our actual production database. I was looking into solutions for this. Is there any plans to regarding this in Prefect OSS? Or its up to the users to manage this by themselves?

I think a couple people recently have asked about managing old data in Prefect OSS. At the moment it is up to the user's to manage themselves if hosting their own setup. However we would definitely welcome a contribution if you're interested? This is the only open issue for it I believe

I opted to using

ALTER TABLE public.log ADD CONSTRAINT fk_log_flow_run_id 
FOREIGN KEY (flow_run_id) REFERENCES flow_run(id) ON DELETE CASCADE;