Commit0c67e9e

committed

Fix typo in MVCC test comment

The optimization is named kill_prior_tuple but was accidentallyspelled kill_prio_tuple in the test.Author: Mingli Zhang <avamingli@gmail.com>Discussion:https://postgr.es/m/82d3e66a-d8ae-4bfa-943e-29c5add0743f@Spark

1 parent4112e39 commit0c67e9eCopy full SHA for 0c67e9e

File tree

-2

lines changed

-2

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1,7 +1,7 @@`
`1`	`1`	`--`
`2`	`2`	`-- Verify that index scans encountering dead rows produced by an`
`3`	`3`	`-- aborted subtransaction of the current transaction can utilize the`
`4`		`---kill_prio_tuple optimization`
	`4`	`+--kill_prior_tuple optimization`
`5`	`5`	`--`
`6`	`6`	`-- NB: The table size is currently not expected to stay the same, we`
`7`	`7`	`-- don't have logic to trigger opportunistic pruning in cases like`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -1,7 +1,7 @@`
`1`	`1`	`--`
`2`	`2`	`-- Verify that index scans encountering dead rows produced by an`
`3`	`3`	`-- aborted subtransaction of the current transaction can utilize the`
`4`		`---kill_prio_tuple optimization`
	`4`	`+--kill_prior_tuple optimization`
`5`	`5`	`--`
`6`	`6`	`-- NB: The table size is currently not expected to stay the same, we`
`7`	`7`	`-- don't have logic to trigger opportunistic pruning in cases like`

Comments

(0)