Re: BUG #2371: database crashes with semctl failed error
От | Brock Peabody |
---|---|
Тема | Re: BUG #2371: database crashes with semctl failed error |
Дата | |
Msg-id | 00d901c658ba$f752fc10$a70a10ac@npci.com обсуждение исходный текст |
Ответ на | Re: BUG #2371: database crashes with semctl failed error ("Qingqing Zhou" <zhouqq@cs.toronto.edu>) |
Ответы |
Re: BUG #2371: database crashes with semctl failed error
|
Список | pgsql-bugs |
> -----Original Message----- > From: pgsql-bugs-owner@postgresql.org [mailto:pgsql-bugs- > owner@postgresql.org] On Behalf Of Qingqing Zhou > Sent: Wednesday, April 05, 2006 6:33 AM > To: pgsql-bugs@postgresql.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
В списке pgsql-bugs по дате отправления: