Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Maxim Sobolev <sobomax(at)sippysoft(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, Konstantin Belousov <kib(at)freebsd(dot)org>
Subject: Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD
Date: 2016-06-22 16:01:41
Message-ID: 1083.1466611301@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Maxim Sobolev <sobomax(at)sippysoft(dot)com> writes:
> From the man semopt:
> [EINVAL] No semaphore set corresponds to semid, or the process
> would exceed the system-defined limit for the number
> of per-process SEM_UNDO structures.

> AFAIK we've been hitting the second cause there. This is with FreeBSD 10.3
> and postgresql 9.2.16 specifically. We've also seen this with 9.1 I think,
> but I am not 100% sure. The specific limit that got exceeded
> was kern.ipc.semmnu.

We never ask semop(2) for SEM_UNDO, so are you sure this isn't a kernel
bug? I've never heard of such a report on any other platform.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Martín Marqués 2016-06-22 17:05:32 Re: pg_dump doesn't dump new objects created in schemas from extensions
Previous Message Maxim Sobolev 2016-06-22 15:47:30 Re: BUG #14206: Switch to using POSIX semaphores on FreeBSD