diff options
author | Daniel Gustafsson | 2022-08-25 08:31:20 +0000 |
---|---|---|
committer | Daniel Gustafsson | 2022-08-25 08:31:20 +0000 |
commit | 0c67e9e566db32df3f420268e81e32f278a2f090 (patch) | |
tree | c28a14eaf66035a461d692b23a7a916cda7f00f4 | |
parent | 4112e39f70eed8d699ea5be7f5945a8970023d0d (diff) |
Fix typo in MVCC test comment
The optimization is named kill_prior_tuple but was accidentally
spelled kill_prio_tuple in the test.
Author: Mingli Zhang <avamingli@gmail.com>
Discussion: https://postgr.es/m/82d3e66a-d8ae-4bfa-943e-29c5add0743f@Spark
-rw-r--r-- | src/test/regress/expected/mvcc.out | 2 | ||||
-rw-r--r-- | src/test/regress/sql/mvcc.sql | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/src/test/regress/expected/mvcc.out b/src/test/regress/expected/mvcc.out index 16ed4ddf2d8..225c39f64f8 100644 --- a/src/test/regress/expected/mvcc.out +++ b/src/test/regress/expected/mvcc.out @@ -1,7 +1,7 @@ -- -- Verify that index scans encountering dead rows produced by an -- aborted subtransaction of the current transaction can utilize the --- kill_prio_tuple optimization +-- kill_prior_tuple optimization -- -- NB: The table size is currently *not* expected to stay the same, we -- don't have logic to trigger opportunistic pruning in cases like diff --git a/src/test/regress/sql/mvcc.sql b/src/test/regress/sql/mvcc.sql index b22a86dc5e5..0a3ebc88f34 100644 --- a/src/test/regress/sql/mvcc.sql +++ b/src/test/regress/sql/mvcc.sql @@ -1,7 +1,7 @@ -- -- Verify that index scans encountering dead rows produced by an -- aborted subtransaction of the current transaction can utilize the --- kill_prio_tuple optimization +-- kill_prior_tuple optimization -- -- NB: The table size is currently *not* expected to stay the same, we -- don't have logic to trigger opportunistic pruning in cases like |