forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commite8d74ad
committed
Report syncscan position at end of scan.
The comment in heapgettup_advance_block() says that it reports thescan position before checking for end of scan, but that didn't matchthe code. The code was refactored in commit7ae0ab0, whichinadvertently changed the order of the check and reporting. Change itback.This caused a few regression test failures with a small shared_bufferssetting like 10 MB. The 'portals' and 'cluster' tests perform seqscansthat are large enough that sync seqscans kick in. When the sync scanposition is not updated at end of scan, the next seq scan doesn'tstart at the beginning of the table, and the test queries aresensitive to that.Reviewed-by: Melanie Plageman, David RowleyDiscussion:https://www.postgresql.org/message-id/6f991389-ae22-d844-a9d8-9aceb7c01a9a@iki.fiBackpatch-through: 161 parentd7ceb41 commite8d74ad
1 file changed
+11
-11
lines changedLines changed: 11 additions & 11 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
647 | 647 |
| |
648 | 648 |
| |
649 | 649 |
| |
650 |
| - | |
651 |
| - | |
652 |
| - | |
653 |
| - | |
654 |
| - | |
655 |
| - | |
656 |
| - | |
657 |
| - | |
658 |
| - | |
659 |
| - | |
660 |
| - | |
661 | 650 |
| |
662 | 651 |
| |
663 | 652 |
| |
| |||
673 | 662 |
| |
674 | 663 |
| |
675 | 664 |
| |
| 665 | + | |
| 666 | + | |
| 667 | + | |
| 668 | + | |
| 669 | + | |
| 670 | + | |
| 671 | + | |
| 672 | + | |
| 673 | + | |
| 674 | + | |
| 675 | + | |
676 | 676 |
| |
677 | 677 |
| |
678 | 678 |
| |
|
0 commit comments
Comments
(0)