![](https://secure.gravatar.com/avatar/99fde0c1dfd216326aae0aff30d493f1.jpg?s=120&d=mm&r=g)
19 Mar
2024
19 Mar
'24
10:12 p.m.
Andrei Elkin
In normal cases, like that of not so many duplicate xids, the size of maybe_active_xid must remain constrained because of "continuous" relocation of elements from the tail to replace garbage (normally found in head indexes).
Nevertheless as the array can be dynamically re-allocated to reflect some some spike in the load, I suggest in
origin/review__knielsen_xa_sched_minimal_fix
to take care of that.
I think your suggestion in review__knielsen_xa_sched_minimal_fix is fine. I'm not sure exactly how large the array can grow in pathological cases. As you wrote, in most normal cases we would expect it to not grow that much. But shrinking it if necessary surely cannot hurt. Thanks, - Kristian.