Re: BUG #2371: database crashes with semctl failed error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Brock Peabody" <brock(dot)peabody(at)npcinternational(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2371: database crashes with semctl failed error
Date: 2006-04-05 14:58:01
Message-ID: 370.1144249081@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Brock Peabody" <brock(dot)peabody(at)npcinternational(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-04-05 14:59:53 Re: PGSTAT: bind(2): Can't assign requested address
Previous Message Pavel Golub 2006-04-05 14:31:04 BUG #2377: pg_constraint didnt't updated when table columns deleted