Re: BUG #2371: database crashes with semctl failed error - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2371: database crashes with semctl failed error
Date
Msg-id 370.1144249081@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #2371: database crashes with semctl failed error  ("Brock Peabody" <brock.peabody@npcinternational.com>)
Responses Re: BUG #2371: database crashes with semctl failed error  ("Brock Peabody" <brock.peabody@npcinternational.com>)
List pgsql-bugs
"Brock Peabody" <brock.peabody@npcinternational.com> writes:
>> Can you reliablly reproduce the problem?

> I can here :).  I'm trying to figure out a way for someone to repeat it
> outside my environment but I'm afraid it's got something to do with
> timing.  I have 50 threads that are collecting data.  If I give each one
> its own connection to the database the problem happens quickly.  If they
> all share one connection the problem does not happen.

Perhaps you could whittle down your app into a testbed that just sends
dummy data with about the same timing as the real app?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Bjoern A. Zeeb"
Date:
Subject: Re: PGSTAT: bind(2): Can't assign requested address
Next
From: Tom Lane
Date:
Subject: Re: PGSTAT: bind(2): Can't assign requested address