1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typo in MVCC test comment

Browse Source 
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
This commit is contained in:
Daniel Gustafsson 2022-08-25 10:31:20 +02:00
parent 4112e39f70
commit 0c67e9e566
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/test/regress/expected/mvcc.out
View File

@ -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

2
src/test/regress/sql/mvcc.sql
View File

@ -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