> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:pgsql-bugs- > [EMAIL PROTECTED] 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 > > > ""Brock Peabody"" <[EMAIL PROTECTED]> 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 > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster
---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
