Experiment with the loose foreign keys feature
With the loose foreign keys feature merged, we can configure the loose foreign keys for the following tables:
- chat_names -> ci_pipeline_chat_data (FK:
fk_rails_f300456b63
) - clusters_applications_runners -> ci_runners (FK:
fk_02de2ded36
)
These tables have low impact, they're not referencing high-traffic tables. According to Thanos, there are tuple deletions so there is a good chance that we'll see items in the deleted_records
table.
As the first phase, the existing foreign keys will not be removed. We want to test if the CleanupWorker
job can keep up with deleted records.
- Add the loose foreign key definition to the models.
- Create migration for adding the tracking
TRIGGER
to the tables.
We have examples in the WIP docs: !72522 (merged)