Check for interrupts during tuple-insertion loops.
Robert Haas <rhaas@postgresql.org>
Check for interrupts during tuple-insertion loops. Normally, this won't matter too much; but if I/O is really slow, for example because the system is overloaded, we might write many pages before checking for interrupts. A single toast insertion might write up to 1GB of data, and a multi-insert could write hundreds of tuples (and their corresponding TOAST data).
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/heap/heapam.c | modified | +2 −0 |
| src/backend/access/heap/tuptoaster.c | modified | +3 −0 |