Fix rescan logic in nodeCtescan.
The previous coding essentially assumed that nodes would be rescanned in
the same order they were initialized in; or at least that the leader of
a group of CTEscans would be rescanned before any others were required to
execute. Unfortunately, that isn't even a
Fix rescan logic in nodeCtescan.
The previous coding essentially assumed that nodes would be rescanned in
the same order they were initialized in; or at least that the leader of
a group of CTEscans would be rescanned before any others were required to
execute. Unfortunately, that isn't even a
Fix rescan logic in nodeCtescan.
The previous coding essentially assumed that nodes would be rescanned in
the same order they were initialized in; or at least that the leader of
a group of CTEscans would be rescanned before any others were required to
execute. Unfortunately, that isn't even a
Fix rescan logic in nodeCtescan.
The previous coding essentially assumed that nodes would be rescanned in
the same order they were initialized in; or at least that the leader of
a group of CTEscans would be rescanned before any others were required to
execute. Unfortunately, that isn't even a
Fix rescan logic in nodeCtescan.
The previous coding essentially assumed that nodes would be rescanned in
the same order they were initialized in; or at least that the leader of
a group of CTEscans would be rescanned before any others were required to
execute. Unfortunately, that isn't even a
