Loading
Implement backend for merge schedule end time
What does this MR do and why?
Implement backend for merge schedule end time
| Changes | MR |
|---|---|
| Most backend changes | |
| Cleanup migrations | !262275 (merged) |
| Frontend & Controller | !258025 (merged) |
References
Related to #630505 (closed)
Screenshots or screen recordings
The frontend is included in a separate MR, screenshots provided here are just for reference
These screenshots might be outdated. For up-to-date screenshots see the frontend MR.
Query for database
SELECT "merge_request_merge_schedules"."merge_after", "merge_request_merge_schedules"."merge_request_id"
FROM "merge_request_merge_schedules"
WHERE
"merge_request_merge_schedules"."merge_after" <= '2026-09-27 17:06:46.364879'
AND ("merge_request_merge_schedules"."merge_before" IS NULL OR "merge_request_merge_schedules"."merge_before" >= '2026-09-27 17:06:46.364885')
ORDER BY "merge_request_merge_schedules"."merge_after" ASC, "merge_request_merge_schedules"."merge_request_id" ASC
LIMIT 500-- page 1: 0.21 ms
Limit (actual time=0.013..0.176 rows=500 loops=1)
Buffers: shared hit=197
-> Index Scan using index_merge_request_merge_schedules_on_merge_after_and_mr_id on merge_request_merge_schedules
Index Cond: (merge_after <= '2026-10-01 09:58:19.346048+00'::timestamp with time zone)
Filter: ((merge_before IS NULL) OR (merge_before >= '2026-10-01 09:58:19.346048+00'::timestamp with time zone))
-- page N: 0.34 ms
Limit (actual time=0.020..0.297 rows=500 loops=1)
Buffers: shared hit=394
-> Index Scan using index_merge_request_merge_schedules_on_merge_after_and_mr_id on merge_request_merge_schedules
Index Cond: ((merge_after <= '2026-10-01 09:58:19.346048+00'::timestamp with time zone) AND (ROW(merge_after, merge_request_id) > ROW('2025-12-31 08:54:00+00'::timestamp with time zone, 443300260)))
Filter: ((merge_before IS NULL) OR (merge_before >= '2026-10-01 09:58:19.346048+00'::timestamp with time zone))MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Niklas van Schrick


