Sync partitions on "other" databases only if not production
What does this MR do and why?
As we need this done only to avoid diffs in structure.sql
in development, we may skip syncing partitions on the "other" database for
production and avoid problems like gitlab-com/gl-infra/production#17997 (comment 1902738958).
See also the original discussion in !91444 (comment 1081684848).
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
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.