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

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2371: database crashes with semctl failed error
Date: 2006-04-05 11:32:53
Message-ID: e10a3h$1s84$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


""Brock Peabody"" <brock(dot)peabody(at)npcinternational(dot)com> wrote
>
> FATAL: semctl(167894456, 4, SETVAL, 0) failed: A non-blocking socket
> operation could not be completed immediately.
>

Can you reliablly reproduce the problem? If so, we may come up with a
testing patch to it. We encounter similar problems before but it is hard to
reproduce.

Magnus? As Bruce suggested, we can plug in a check-EINTR-loop here in
semctl():

/* Quickly lock/unlock the semaphore (if we can) */
if (semop(semId, &sops, 1) < 0)
return -1;

Regards,
Qingqing

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Qingqing Zhou 2006-04-05 11:39:27 Re: contrib/intarray/_int_gist.c
Previous Message 维 姜 2006-04-05 11:32:29 contrib/intarray/_int_gist.c