Skip to content

Do not confuse databases in sliding list strategy

Simon Tomlinson requested to merge wrong-connection-fixing-sliding-list-partitions into master

What does this MR do and why?

Do not confuse databases in sliding list strategy

The sliding list strategy's validate_and_fix method could compare the column default in the model's database to the current partition in the currently active shared database. This led to changing the default incorrectly, and flip-flopping it the next time the partition manager ran.

Stops the problem in #414541 (closed) by never running validate_and_fix with mismatched connections.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

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

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