From: | "Brock Peabody" <brock(dot)peabody(at)npcinternational(dot)com> |
---|---|
To: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #2371: database crashes with semctl failed error |
Date: | 2006-04-05 14:12:26 |
Message-ID: | 00d901c658ba$f752fc10$a70a10ac@npci.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> -----Original Message-----
> From: pgsql-bugs-owner(at)postgresql(dot)org [mailto:pgsql-bugs-
> owner(at)postgresql(dot)org] On Behalf Of Qingqing Zhou
> Sent: Wednesday, April 05, 2006 6:33 AM
> To: pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] BUG #2371: database crashes with semctl failed
> error
> 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.
> If so, we may come up with a
> testing patch to it. We encounter similar problems before but it is
> hard to reproduce.
Do you think this is a Windows only problem?
Thanks,
Brock
From | Date | Subject | |
---|---|---|---|
Next Message | Bjoern A. Zeeb | 2006-04-05 14:16:24 | Re: PGSTAT: bind(2): Can't assign requested address |
Previous Message | Brock Peabody | 2006-04-05 14:03:20 | Re: BUG #2371: database crashes with semctl failed error |