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

From Brock Peabody
Subject Re: BUG #2371: database crashes with semctl failed error
Date
Msg-id 010601c658ca$d9b5db90$a70a10ac@npci.com
Whole thread Raw
In response to Re: BUG #2371: database crashes with semctl failed error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> On Behalf Of Tom Lane

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

I think I'm starting to get a better understanding of problem.  It looks
like one of the threads is trying to insert a pathological (~1,800,000)
number of records in one transaction in a table while the other threads
are also reading from and writing to that table.  I'll try to get
something simple to reproduce this behavior.

pgsql-bugs by date:

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