Re: Problem with locks - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Problem with locks
Date
Msg-id 87zm0wzwxs.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Problem with locks  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Problem with locks
Re: Problem with locks
Re: Problem with locks
List pgsql-hackers
"Gregory Stark" <stark@enterprisedb.com> writes:

> "Gregory Stark" <stark@enterprisedb.com> writes:
>
>> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
>>
>>> Gregory Stark <stark@enterprisedb.com> writes:
>>>> We're seeing a problem where occasionally a process appears to be granted a
>>>> lock but miss its semaphore signal.
>>>
>>> Kernel bug maybe?  What's the platform?

I've written a synthetic test program to check for lost semaphore wakeups. I
can't seem to produce any on my machine but haven't had a chance to run it yet
on the benchmark machine that's been showing the problem.

If I can't produce any lost wakeups with a program like this it looks more
like it might be a Postgres or GCC bug than a Linux bug.

It would be helpful if people could run this on various architectures and
various versions of Linux (or other OSes). I've been running it with 40
processes for an hour, but even shorter runs would be useful. It will drive
the load on your machine through the roof but doesn't cause any i/o.

$ gcc -Wall ipctest.c -lrt
$ ./a.out 40 3600


--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proper way to fix information_schema.key_column_usage view
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: Problem with locks