Re: Assert failure found in 8.1RC1 - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Assert failure found in 8.1RC1
Date
Msg-id 20051108200958.GS19551@pervasive.com
Whole thread Raw
In response to Re: Assert failure found in 8.1RC1  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: Assert failure found in 8.1RC1  (Robert Creager <Robert.Creager@Sun.com>)
List pgsql-hackers
On Fri, Nov 04, 2005 at 08:46:27PM -0400, Marc G. Fournier wrote:
> On Fri, 4 Nov 2005, Jim C. Nasby wrote:
> For all the talk about "couldn't it be part of regression", I haven't seen 
> anyone submit a patch that would test for it ... since I believe both you 
> and Tom have both stated that "for things like race conditions, I don't 
> know that you can create reproducable cases", can you submit a patch for 
> how you propose this should be added to the regression tests?

I have an idea, but it might be better if Robert could produce a test
case since it would cover both a context storm issue as well as this
race condition.

Baring that, my idea was to spawn a number of processes, all of which
were trying to insert/update a random value in a table using David
Fetter's plpgsql code for doing a merge. This would produce a heavy
workload that also used subtransactions (due to the exception handling
in plpgsql).

Suggestions for a better test welcome...
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Robert Creager
Date:
Subject: Re: SIGSEGV taken on 8.1 during dump/reload
Next
From: Gavin Sherry
Date:
Subject: lc_numeric and decimal delimiter