supabase / storage / 42638962293

88%

push

github

fix: sort in migration batcher to reduce deadlocks (#1682)

## What kind of change does this PR introduce?

Bug fix

## What is the current behavior?

Progressive sends each selected batch in the order of requests added
tenants. Full-fleet sends each batch in scan-cursor order. Overlapping
batches can therefore reach queue with tenant keys in opposite orders
and deadlock.

## What is the new behavior?

Both senders sort each batch by tenant before submitting it. Progressive
still selects tenants in arrival order and full-fleet pagination is
unchanged.

## Additional context

This reduces the observed ordering conflict but does not guarantee
deadlock freedom because pg can reorder.

Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>

8464 of 10169 branches covered (83.23%)

Branch coverage included in aggregate %.

1 of 1 new or added line in 1 file covered. (100.0%)

14437 of 15985 relevant lines covered (90.32%)

1298.45 hits per line