Tom Lane <tgl@sss.pgh.pa.us> wrote:
> What this suggests is that CLOBBER_CACHE_ALWAYS is actually too
> strong to provide a thorough test of cache flush hazards. Maybe
> we need an alternate setting along the lines of
> CLOBBER_CACHE_SOMETIMES that would randomly choose whether or not
> to flush at any given opportunity. But if such a setup did produce
> a crash, it'd be awfully hard to reproduce for investigation.
> Ideas?
Seed the random number generator such that each run of the test gets
the same "random" numbers? Or *allow* the seed to be set, with the
default being a random seed which is logged so that it can be forced
for a repeat of the run?
-Kevin
