From: Daniel Gustafsson Date: Thu, 25 Aug 2022 08:31:20 +0000 (+0200) Subject: Fix typo in MVCC test comment X-Git-Tag: REL_16_BETA1~1885 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=0c67e9e566db32df3f420268e81e32f278a2f090;p=thirdparty%2Fpostgresql.git 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 Discussion: https://postgr.es/m/82d3e66a-d8ae-4bfa-943e-29c5add0743f@Spark --- 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