Re: Flaky vacuum truncate test in reloptions.sql
Arseny Sher <a.sher@postgrespro.ru>
From: Arseny Sher <a.sher@postgrespro.ru>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-01T03:08:28Z
Lists: pgsql-hackers
Masahiko Sawada <sawada.mshk@gmail.com> writes: >> I don't think this matters much, as it tests the contrary and the >> probability of >> successful test passing (in case of theoretical bug making vacuum to >> truncate >> non-empty relation) becomes stunningly small. But adding it wouldn't hurt >> either. > > I was concerned a bit that without FREEZE in the first VACUUM we could > not test it properly because the table could not be truncated because > either vacuum_truncate is off FREEZE won't help us there. > or the page is skipped. You mean at the same time there is a potential bug in vacuum which would force the truncation of non-empy relation if the page wasn't locked? That would mean the chance of test getting passed even single time is close to 0, as currently the chance of its failure is close to 1. -- cheers, arseny
Commits
-
Improve stability of test with vacuum_truncate in reloptions.sql
- bada6280f0b9 12.7 landed
- 89937d001294 13.3 landed
- fe246d1c111d 14.0 landed