Skip to content

Sliding list partitioning strategy

Simon Tomlinson requested to merge sliding-list-partitioning-strategy into master

What does this MR do and why?

This is the first step in #343084 (closed). It implements a sliding list partitioning strategy that can be used for queue-like tables.

A sliding list strategy creates new partitions on a schedule, and then drops old partitions when they are no longer necessary. By doing this, we can avoid high vacuuming costs that we would incur if we just deleted the rows from a single table.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

This is difficult to validate because there are no users of the strategy yet. You could check out !73408, which is still in-progress but applies this strategy to loose_foreign_keys_deleted_records, and follow the instructions there to validate.

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 Simon Tomlinson

Merge request reports