diff options
Diffstat (limited to 'src/test/isolation')
| -rw-r--r-- | src/test/isolation/expected/vacuum-reltuples.out | 2 | ||||
| -rw-r--r-- | src/test/isolation/specs/vacuum-reltuples.spec | 7 |
2 files changed, 5 insertions, 4 deletions
diff --git a/src/test/isolation/expected/vacuum-reltuples.out b/src/test/isolation/expected/vacuum-reltuples.out index cdbe7f3a60..ce55376e7f 100644 --- a/src/test/isolation/expected/vacuum-reltuples.out +++ b/src/test/isolation/expected/vacuum-reltuples.out @@ -45,7 +45,7 @@ step stats: relpages|reltuples --------+--------- - 1| 20 + 1| 21 (1 row) diff --git a/src/test/isolation/specs/vacuum-reltuples.spec b/src/test/isolation/specs/vacuum-reltuples.spec index ae2f79b8fe..a2a461f2f5 100644 --- a/src/test/isolation/specs/vacuum-reltuples.spec +++ b/src/test/isolation/specs/vacuum-reltuples.spec @@ -2,9 +2,10 @@ # to page pins. We absolutely need to avoid setting reltuples=0 in # such cases, since that interferes badly with planning. # -# Expected result in second permutation is 20 tuples rather than 21 as -# for the others, because vacuum should leave the previous result -# (from before the insert) in place. +# Expected result for all three permutation is 21 tuples, including +# the second permutation. VACUUM is able to count the concurrently +# inserted tuple in its final reltuples, even when a cleanup lock +# cannot be acquired on the affected heap page. setup { create table smalltbl |