From looking at this patch and its history [1, 2], I think momentum was
probably lost during the January CF, where this patch was unregistered
(presumably by accident).
I've carried it forward, but it needs some help to keep from stalling
out. Definitely make sure it's rebased and up to date by the time the
next CF starts, to give it the best chance at getting additional review
(if you haven't received any by then).
--Jacob
[1] https://commitfest.postgresql.org/34/3258/
[2] https://commitfest.postgresql.org/38/3537/
