pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s

pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s

pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s

pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s

pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s

pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s

pgsql: Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem.

2025-08-26 Thread Tom Lane
Do CHECK_FOR_INTERRUPTS inside, not before, scanGetItem. The CHECK_FOR_INTERRUPTS call in gingetbitmap turns out to be inadequate to prevent a long uninterruptible loop, because we now know a case where looping occurs within scanGetItem. While the next patch will fix the bug that caused that, it s