forked from greenplum-db/gpdb-archive
-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix vacuum_progress isolation tests Isolation tests vacuum_progress_column and vacuum_progress_row would previously fail sometimes because vacuum_worker_changed fault injector was never reached. This happened because vacuum execution and FTS version upgrade are not synchronized: after FTS disables syncrep according to the test, it should bump FTS version, which should be detected by the dispatcher on the next StartTransaction call, and then the segment backends will be restarted (making vacuum_worker_changed fault accessible). However, if FTS is too slow (or dispatcher too fast), it might skip StartTransaction calls before FTS version is bumped, and the segment restart will happen after vacuum is complete, without triggering vacuum_worker_changed. This is an acceptable behavior for the code since the restart still happens milliseconds after disabling syncrep, but the test doesn't expect it. This patch fixes the test by making the dispatcher wait on vacuum_rel_finished_one_relation fault until waits until mirror down is detected by FTS, ensuring FTS version bump happens before dispatcher proceeds. Note that the patch also changes expected output: it seems like previously restart happened on the last StartTransaction, making all the collected stats to be zero. However, post-cleanup vacuum phase (which is executed after vacuum_worker_changed) is also responsible for vacuuming the indexes, so the correct output should include those too. Note that num_dead_tuples value is still zero, indicating that vacrelstats was indeed reset correctly.
- Loading branch information
1 parent
e8aa067
commit e60a012
Showing
4 changed files
with
60 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters