From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Cache-flush stress testing |
Date: | 2006-01-19 22:11:26 |
Message-ID: | 20060119221126.GI78403@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 19, 2006 at 05:03:20PM -0500, Tom Lane wrote:
> I'm still bothered by the likelihood that there are cache-flush bugs in
> code paths that are not exercised by the regression tests. The
> CLOBBER_CACHE patch is far too slow to consider enabling on any regular
> basis, but it seems that throwing in cache flushes at random intervals,
> as in the test program I posted here:
> http://archives.postgresql.org/pgsql-hackers/2006-01/msg00244.php
> doesn't provide very good test coverage. Has anyone got any ideas about
> better ways to locate such bugs?
Some of the machines in the buildfarm do nothing else useful, if this
was turned into a configure option it would be trivial to setup some of
those machines to just hammer away at this.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-19 22:11:56 | Re: un-vacuum? |
Previous Message | Tom Lane | 2006-01-19 22:03:20 | Cache-flush stress testing |