On 2026-Sep-21, Alvaro Herrera wrote:
> Yeah, maybe this approach isn't great after all. We could turn that
> around and search for each loop around the snap->xmin..snap->xmax loop
> that is found in snap->xip in the running->xids array. That reduces the
> number of times we go through XactLockTableWait() to only running
> transactions (same as in Rui's original patch [1]). However, the
> running->xids array is not sorted, so we would have to qsort() it, or do
> a plain array walk for each element.
BTW just to make it clear what I'm talking about, attached is the patch
for this approach, which I'm now thinking to throw away in favor of
Rui's earlier version. (The test contains the change Rui suggested
yesterday, and it's passing for me with this patch.) I didn't touch the
commit message.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Las cosas son buenas o malas segun las hace nuestra opinión" (Lisias)
