From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Rusty Conover" <rconover(at)infogears(dot)com>, <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [BUGS] BUG #5412: test case produced, possible race condition. |
Date: | 2010-04-14 18:39:19 |
Message-ID: | 4BC5C58702000025000308C8@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Rusty Conover | 2010-04-14 18:59:47 | Re: [BUGS] BUG #5412: test case produced, possible race condition. |
Previous Message | Tom Lane | 2010-04-14 18:31:44 | Re: [BUGS] BUG #5412: test case produced, possible race condition. |
From | Date | Subject | |
---|---|---|---|
Next Message | Rusty Conover | 2010-04-14 18:59:47 | Re: [BUGS] BUG #5412: test case produced, possible race condition. |
Previous Message | Tom Lane | 2010-04-14 18:31:44 | Re: [BUGS] BUG #5412: test case produced, possible race condition. |