Skip to content

[Draft] PoC Partition `security_findings` table

What does this MR do and why?

This is just a PoC to discuss the actual implementation plan and this MR will probably be split into smaller parts which span over multiple milestones.

The idea is to partition the security_findings table into around 10GB sizes to make it easier to purge the stale records(Related to Implement retention period for Security::Findin... (#351524 - closed)).

We choose the list partitioning strategy which will work like a sliding window and the partitions staying on the left side of the window will be detached automatically.

sliding_window

The main difference from the current SlidingListPartitioning strategy is that the partition_number is set by the application instead of relying on the default value of the column to make sure all the records for a pipeline land into the same partition to prevent reading from multiple partitions.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Mehmet Emin INAC

Merge request reports